Skip Navigation

[Closed] WordPress 5.6 Compatibility error

This support ticket is created 4 years, 7 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.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 4 years, 7 months ago.

Assisted by: Christian Cox.

Author
Posts
#1899661

When Go Daddy automatically upgraded my site -- hidden link -- to WordPress 5.6, the whole site when down due to an incompatibility with types3.4.5. Here is what I am running:

WordPress version 5.6
Current theme: Community Home Trust (version 1.0)
Current plugin: Toolset Types (version 3.4.5)
PHP version 7.3.12

If I activate the plugin, the site fails and I need to deactivate it through PHPmyAdmin. As soon as Types is disabled, the site is back up and running but without my custom post types which I need for the site to function properly.

Please let me know what I can do to reinstate the plugin without causing other problems.

#1900251

Hi, sorry to hear you are experiencing a problem after updating the site. I'll be glad to take a closer look.

I'd like to point out that it is possible to temporarily deactivate a plugin without manipulating the database directly. You can use FTP to rename the plugin directory instead. For your reference, the Types plugin can be found in /wp-content/plugins. The folder name is "types", so you can deactivate the plugin by renaming it to something like "types-backup" temporarily.

Let's try to find out more about why the site is crashing after updating. There are no inherent conflicts between Types and WP 5.6, so there must be something else going on. First, I'd like to know if there is a conflict between Toolset and the site's theme, or other active plugins. Please try this test:
- Temporarily activate a default theme like Twenty Twenty One
- Temporarily deactivate all plugins, and then activate Types by itself
- If the site does not crash, reactivate the theme and other plugins one by one until the site crashes again. If the site theme is a child theme, activate the parent theme first before testing the child theme. Note which component you activated before the crash was triggered.
- If the site crashes after deactivating all plugins except Types and activating a default theme, it's possible there was a problem during the update process and the Types plugin was not fully updated or installed correctly. Please temporarily deactivate Types and then delete the Types plugin from wp-admin > Plugins > Installed Plugins. Download a fresh copy of Types from https://toolset.com/account/downloads, and install it at wp-admin > Plugins > Add New. Try to activate once again. If the site crashes, we need to check the server logs to determine the cause of the crash.
- If you are not familiar with server logging, I can show you how to turn on a temporary log and get more information about server crashes. This code assumes you have a standard wp-config.php file with no significant modifications from wp-config-sample.php. Edit your wp-config.php file and look for

define('WP_DEBUG', false);

Change it to:

define('WP_DEBUG', true);

Then add these lines, just after the WP_DEBUG line:

define('WP_DEBUG_LOG', dirname(__FILE__) . '/error_log.txt');
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);

Then try activating Types again. When a server-side error is thrown, the system will write more information about that failure into a file called error_log.txt in the main directory of the site, typically in the same directory where you find wp-config.php. If you're using FTP, you may need refresh that directory to see the file appear.

Please download that file to your computer and open it with any text editing software. Copy its contents and paste them in your next reply. Then you can delete the error_log.txt file from the server and revert any changes you made in wp-config.php.

The topic ‘[Closed] WordPress 5.6 Compatibility error’ is closed to new replies.