Update Crashed My Site

Is there any way for you to retrieve and review error logs for the site? That’s going to be the best first step to start investigating for what’s going on.

Was CPTUI one of the updated plugins? or were the updated ones other items?

Hey Michael,

Thank you for your quick response. Apologies for the delay in responding i was backing up my website to prior the crash to see which plugins were updated.

So CPTUI was not updated, the plugins which were updated were:

Really Simple SSL
Trust Payments Gateway for WooCommerce
W3 Total Cache
Woocommerce
Yoast SEO

So what happened was, I updated all of these and the website crashed. I attempted to diagnose the issue by deactivating each plugin one by one and found the culprit to be CPTUI. The website goes partially back to normal but not fully. Not sure why this is happening. Attemtped to ‘Rollback” the update of CPTUI to an older version but still not resolution.

I could not derive any error logs.

If it helps, last night when the plugins updated i received an email stating that wordpress detecting an issue with W3 total cache. In two minds whether i should reset all setting in W3 to see how that goes – what are your thoughts?

So i have just deactivated every other plugin and it seems like Custom Type Post UI is the anomaly. It is conflicting with one of the updated plugins.

I hope this can get updated soon. Thanks

Hi again,

Really hard for me to do any updates for anything, without knowing what’s going on or the errors being experienced. So there’s not really something for me to push code wise.

So you don’t have anything in error logs through your hosting provider? Do you have access to your wp-config.php file so that we could turn on some debugging constants that may provide more information?

Yes, i can access the wp-config.php. I changed the following:

define( ‘WP_DEBUG’, false );
to
define( ‘WP_DEBUG’, true );

and no errors were presented on the front end of the website. If you can kindly provide guidance on how to turn on debugging i can do this.

Many thanks.

That should turn the debugging on for you already, including hopeful error display. The next question would be triggering the error again, which I assume is going to be a matter of re-activating CPTUI and letting things run.

Michael,

Many thanks for your support the full day – I appreciate you trying to help me.

This is the error in question:

Warning: include(/customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/vendor/composer/../../admin/class-yoast-notifications.php): Failed to open stream: No such file or directory in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/official-facebook-pixel/vendor/composer/ClassLoader.php on line 444 Warning: include(): Failed opening '/customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/vendor/composer/../../admin/class-yoast-notifications.php' for inclusion (include_path='.:/usr/share/php') in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/official-facebook-pixel/vendor/composer/ClassLoader.php on line 444 Fatal error: Uncaught Error: Class "Yoast_Notifications" not found in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo-main.php:434 Stack trace: #0 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo.php(50): require_once() #1 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-settings.php(409): include_once('/customers/7/8/...') #2 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-config.php(116): require_once('/customers/7/8/...') #3 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-load.php(50): require_once('/customers/7/8/...') #4 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-admin/admin.php(34): require_once('/customers/7/8/...') #5 {main} thrown in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo-main.php on line 434 Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-includes/functions.php on line 5535 Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-includes/functions.php on line 5535

I hope this can shed some light on the situation.

Tony

This is the biggest part that I can see:

Fatal error: Uncaught Error: Class "Yoast_Notifications" not found in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo-main.php:434

Stack trace:

#0 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo.php(50): require_once()
#1 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-settings.php(409): include_once('/customers/7/8/...')
#2 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-config.php(116): require_once('/customers/7/8/...')
#3 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-load.php(50): require_once('/customers/7/8/...')
#4 /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-admin/admin.php(34): require_once('/customers/7/8/...')
#5 {main} thrown in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/wordpress-seo/wp-seo-main.php on line 434

I’d say grab a fresh copy of Yoast SEO plugin and re-upload that and try again.

Not quite sure why activating CPTUI could potentially be causing this error/issue, but it’s the one that stands out the most to me.

I have to believe trying to activate Yoast again would also cause errors.

Another error has been brought up upon attemting to ‘Rollback’ the updated plugins in an attempt to see which is the one conflicting with CPTUI:

Warning: The magic method Vc_Manager::__wakeup() must have public visibility in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php on line 203 Deprecated: Required parameter $width follows optional parameter $attach_id in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/helpers/helpers.php on line 366 Deprecated: Required parameter $height follows optional parameter $attach_id in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/helpers/helpers.php on line 366 Deprecated: Required parameter $message follows optional parameter $notice_type in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/easy-login-woocommerce/includes/xoo-el-functions.php on line 82 Warning: Cannot modify header information – headers already sent by (output started at /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php:203) in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-includes/functions.php on line 6584 Warning: Cannot modify header information – headers already sent by (output started at /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php:203) in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-admin/includes/misc.php on line 1310 Warning: Cannot modify header information – headers already sent by (output started at /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php:203) in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-admin/admin-header.php on line 9 Warning: Trying to access array offset on value of type bool in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/themes/Impreza/common/admin/functions/functions.php on line 102

When you say grab a fresh copy, you mean delete and install the plugin again, right?

Warning: Trying to access array offset on value of type bool in /customers/7/8/1/wejustraffle.co.uk/httpd.www/wp-content/themes/Impreza/common/admin/functions/functions.php on line 102

This is another error which is presented in the WP-Admin dashboard. Sorry for bombarding you with errors just trying to establish the source of error.

When you say grab a fresh copy, you mean delete and install the plugin again, right?

Yes

So far I’m not seeing anything at all coming directly from Custom Post Type UI, but definitely things from other plugins.

Also so far the only ones I can see that would prevent a site from loading at all is the Fatal error from Yoast, as well as the “headers already sent” one which appears to be coming from Visual Composer plugin. HOWEVER that one would also potentially be un-triggered by turning off the debugging, because that part is sending output to the browser. A side effect of us trying to debug larger issues.

Not sure how live the site is or how much traffic it gets, but if at all possible, can you confirm that it all loads as expected if JUST Custom Post Type UI is active on the plugin side of things?

That said I think the biggest culprit here is Yoast not having everything it needs somehow.

Hello Michael,

Thank you for your response.

I have deactivated all off the plugins except CPTUI and the page is showing just code but seems to load fine, of course it doesn’t look the way it should.

The only way I can get it to look the way it should is by turning off CPTUI. I have tried to turn off the plugin which you believe to be the main culprit (YOAST SEO) nothing changes in terms of the appearance.

I have also tried to delete YOAST SEO and re-download and again, nothing happens.

As mentioned, the only way i can get the site to look the way it was and functioning correctly again is to deactivate CPTUI which I use for the ‘Winner’ Section of my website.