I had to deactivate WP Foro temprorarily because my webhost critizised that the plugin makes SQL queries that make the the server crash eventually. It looks like a maintenance job the plugin is doing. See below. Anybody an Idea how to solve that issue?
| 243059 | akilifod_wp5 | p21.server.hostpoint.internal:53344 | akilifod_wp5 | Query | 3735 | Storing result in query cache | WITH RECURSIVE `forum_path` AS(
SELECT `forumid`, `parentid`, 0 AS `depth`
FROM `wp_wpforo_forums`
WHERE `forumid` = 3
UNION
SELECT f.`forumid`, f.`parentid`, `depth` + 1
FROM `wp_wpforo_forums` f
INNER JOIN `forum_path` fp ON fp.`parentid` = f.`forumid`
) SELECT `forumid` FROM `forum_path` ORDER BY `depth` DESC | 0.000 |
I doubt wpForo is killing any mysql server.
What kind of hosting plan is that? Can you give us some details?
Do you have Debug to a LOG enabled for Wordpress?
Are there any fatal or other errors in the debug.log?
I haven't got a debug log set up. The hosting is a normal business hosting where up 10 a 100 Domains, 100 Databases and 500 GB of storage can be hosted. I can install adebug log and activate WP Foro again. But it is definitely WP Foro causing the issue because since I deactivated it, the problem stopped.
Just enable debug to a log
Add these to your wp-config.php
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_DISPLAY', false ); define( 'WP_DEBUG_LOG', true );
Also check forums/tools/debug and go through all the tabs to see any issues.
Could you please let us login and help to fix this issue?
Please send the admin login details to support[at]gvectors.com email address.
@robert yep, done, you should have it.
We've not received any email from you. Please check the email again. Make sure you've sent the details to support[at]gvectors.com email address.
@robert yes sure, let me have a look again.
@zimi ,
We found and fixed the issue. Somehow, one of your forum parent ID was set its own ID, so it was stacked in a loop. I think this was a result of some database manipulation by someone. wpForo could not set such parent ID in its own.
@robert many thanks for that. We will never know what caused it but I am glad it's solved.