[Resolved] Types 3.3.7 crashes my test WordPress instance

[Author]

Posts

[Daryl Hatton]

Update: I tried 3.3.6 and it no longer crashes on installation but still crashes on activation. Went back to 3.2.3 and it finally works.

I am trying to: Install Types 3.3.7

Link to a page where the issue can be seen: not published because it crashes site with 500 code

I tried to load new plugin into my site. Plugin uploaded but on next page refresh site returned a HTTP 500 code. Not even activated yet.

I testing loading the new plugin on a completely fresh WordPress install - no other plugins except ServerInfo. Default theme. Same issue.

Manually disabling the plugin allows me to regain access.

Screen shot from ServerInfo attached.

We know we need to upgrade PHP and then WordPress but can't do that yet until we can fire up this new instance that we are using to test all of our plugins, configurations and theme (Themeco Pro) and get everything working under some of the new updated plugins. Lots of moving parts.

I can't provide FTP access at this time given this is on a production server (although not a production WP instance i.e. just for testing).

Thanks for your help.

[Christian Cox]

Hi, PHP 5.6+ is a requirement to run Toolset: https://toolset.com/toolset-requirements/

You'll have to update PHP before you can run the latest versions of Toolset on your test environment fully and effectively, or downgrade Toolset to older versions. But if you're experiencing an error without even activating the plugin, something else is going on. Can you turn on server logs to get more information about the error? If you're not familiar with server logs, or if your host doesn't have them readily available, I can show you how to activate them temporarily.

Go in your wp-config.php file and look for

define('WP_DEBUG', false);

If you find it, 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 );

Now try to upload the plugin again. If there is a backend error generated, this will create an error_log.txt file in your site's root directory. Please open that file in any text editor, copy its contents and send them in your next reply. Once that is done, you can revert the changes you made to wp-config.php and delete the log file.

[Daryl Hatton]

My issue is resolved now. Thank you!