Skip Navigation

[Resolved] Troubleshooting "Critical Error" message on site that was migrated.

This support ticket is created 2 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 5 replies, has 2 voices.

Last updated by matthewS-8 2 years, 4 months ago.

Assisted by: Waqar.

Author
Posts
#2231947

Tell us what you are trying to do?
Create new post, page, type, etc....

Is there any documentation that you are following?
No, troubleshooting blind here.

Is there a similar example that we can see?

What is the link to your site?
rturbanhomes.com

#2232073

Waqar
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting us and sorry to learn about the difficulty you're having.

The "Critical error" in WordPress is very generic and can be caused by a number of reasons.

Have you checked the server's error log for any detailed errors or warnings? A good place to start would be to turn on WordPress debugging and then check for any errors or warnings:
https://wordpress.org/support/article/debugging-in-wordpress/

You'll find some useful troubleshooting steps in this guide:
hidden link

I hope this helps and please let me know how it goes.

regards,
Waqar

#2232383

Thanks Waqar -

I did go through the checklist and did all of those items (increased memory, checked server configurations, etc.

It seems that the error is related to activation of toolset. Here is a dump of the debug log. Obviously Contact Form 7 is one issue I need to tackle, but more importantly, see the PHP errors related to Toolset Views (wp-views).

(Log record)
[28-Nov-2021 21:52:53 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:53 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:53 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:54 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:54 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:54 UTC] PHP Deprecated: wpcf7_add_shortcode is deprecated since Contact Form 7 version 4.6! Use wpcf7_add_form_tag instead. in /home/yw6s0a37jyt3/public_html/wp-content/plugins/contact-form-7/includes/functions.php on line 540
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 7358
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 7359
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'ID' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 7363
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 7605
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/theme.php on line 3421
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Controllers/Admin/ContentTemplate.php on line 78
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/stream/connectors/class-connector-posts.php on line 169
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/theme.php on line 3645
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 5148
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'ID' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 5148
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-includes/post.php on line 4457
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/eventon-rsvp/includes/admin/evo-rsvp_meta_boxes.php on line 391
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/eventON/includes/admin/post_types/class-meta_boxes.php on line 871
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/eventON/includes/admin/post_types/ajde_events.php on line 584
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/total-theme-core/inc/lib/wpex-color-palette/class-wpex-color-palette.php on line 276
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/types/vendor/toolset/toolset-common/user-editors/editor/screen/gutenberg/backend.php on line 639
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields-post.php on line 687
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_status' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Services/ViewParsingService.php on line 158
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_type' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Services/ViewParsingService.php on line 161
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_content' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Services/ViewParsingService.php on line 166
[28-Nov-2021 21:52:55 UTC] PHP Notice: Trying to get property 'post_content' of non-object in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Services/ViewParsingService.php on line 107
[28-Nov-2021 21:52:55 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to OTGS\Toolset\Views\Controllers\Admin\ContentTemplate::set_default_content_template_meta() must be an instance of WP_Post, null given, called in /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php on line 303 and defined in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Controllers/Admin/ContentTemplate.php:138
Stack trace:
#0 /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php(303): OTGS\Toolset\Views\Controllers\Admin\ContentTemplate->set_default_content_template_meta(0, NULL, false)
#1 /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
#2 /home/yw6s0a37jyt3/public_html/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#3 /home/yw6s0a37jyt3/public_html/wp-includes/post.php(4479): do_action('wp_insert_post', 0, NULL, false)
#4 /home/yw6s0a37jyt3/public_html/wp-admin/includes/post.php(694): wp_insert_post(Array, false, false)
#5 /home/yw6s0a37jyt3/public_html/wp-admin/post-new.p in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Controllers/Admin/ContentTemplate.php on line 138

#2232389

Wordpress Error Details
=============
An error of type E_ERROR was caused in line 138 of the file /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Controllers/Admin/ContentTemplate.php. Error message: Uncaught TypeError: Argument 2 passed to OTGS\Toolset\Views\Controllers\Admin\ContentTemplate::set_default_content_template_meta() must be an instance of WP_Post, null given, called in /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php on line 303 and defined in /home/yw6s0a37jyt3/public_html/wp-content/plugins/wp-views/backend/Controllers/Admin/ContentTemplate.php:138
Stack trace:
#0 /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php(303): OTGS\Toolset\Views\Controllers\Admin\ContentTemplate->set_default_content_template_meta(0, NULL, false)
#1 /home/yw6s0a37jyt3/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
#2 /home/yw6s0a37jyt3/public_html/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#3 /home/yw6s0a37jyt3/public_html/wp-includes/post.php(4479): do_action('wp_insert_post', 0, NULL, false)
#4 /home/yw6s0a37jyt3/public_html/wp-includes/revision.php(334): wp_insert_post(Array, true)
#5 /home/yw6s0a37jyt3/public_html/wp-admin/includes/post.php(18

#2232925

Waqar
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for sharing these details.

The errors alone are not very conclusive, so to troubleshoot this further, I'll suggest the following steps:

1. Please make sure that WordPress, active theme, and plugins are all updated to the latest versions.

2. It would be interesting to test this with all non-Toolset plugins disabled and a default theme like Twenty Twenty-One.

If it's fixed, you can start adding the disabled items, one by one, to narrow down to a possible conflicting one.

3. In case the issue still persists, I'll need to see how different Toolset settings and content templates are set up in the admin area. You're welcome to share temporary admin login details along with the exact steps to see the error.

I'll also need your permission to download a clone/snapshot of the website, if this needs to be investigated on a different server.

Note: Your next reply will be private and it is recommended to make a complete backup copy, before sharing the access details.

#2233377

My issue is resolved now. Thank you! I believe the issue was the hosting environment was undersized for the complexity of the site, and the database had errors. We moved the site to a Virtual Private Server with enough resources and replaced it with the dev db in the new hosting environment, everything resolved. Thanks for your assistance!!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.