Skip Navigation

[Resolved] Frequent 500/404 when Toolset is active

This thread is resolved. Here is a description of the problem and solution.

Problem:

The issue here is that the user was getting Frequent 500/404 errors.

Solution:

In this user's case they were using php version 5.6 . Toolset is generally compatible with this version of toolset however it could be multiple issues that was causing this.

Wordpress recommends at least php 7.0 so I recommend that you update to at least this version.

This support ticket is created 5 years, 6 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
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 2 replies, has 2 voices.

Last updated by perryL 5 years, 6 months ago.

Assisted by: Shane.

Author
Posts
#1255105
backend-404.png
waterfall-html-request.png
waterfall-500-404.png

I am trying to: use Access, Forms, Types, and Views. When any of these four plugins are active along with any other plugin on the site, the whole site and backend are prone to sluggishness, long loads, and sometimes unloaded pages. Every time a page loads, in the waterfall, I see at least one 500 error on server requests that takes between 6 and 30 seconds to process. The second html request in the waterfall always takes a decent chunk of time even if it doesn't throw a 500 error. I've attached screenshots of one waterfall from a page load if it helps.

There are also frequent 404 errors when loading pages while navigating the backend. I've attached a screenshot of such a 404 error that I got when trying to generate the Toolset debugger.

These issues go away when deactivating all 4 Toolset plugins, and return if any one of them is reactivated. Also, if only the 4 Toolset plugins are active, but no others are, these issues go away, but that solutions isn't really tenable.

I've turned on WP_DEBUG but don't get any memory errors. I tried increasing the memory to 512M anyway but there was no change.

Are there any other steps I take to try to resolve these issues? Thanks!

#1255193

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Perry,

The first thing I would check is the php logs for the site to see if there are any errors being logged there from toolset.

Secondly I would update the server's php version to version 7.0 or greater as this is now the minimum requirements for wordpress.

It may not be a case where toolset alone is the culprit but incompatibility with php version 5.6 as well.

This is what I would try doing first.

Please let me know if this helps.
Thanks,
Shane

#1255431

PHP 7.2 helped immediately and drastically. Thanks so much!