Background of the issue:
I am trying to resolve an issue with my WordPress website, which has not been working properly for a few weeks. An error message appeared in my admin space indicating a problem with some tables in the database and suggesting I contact WPML support. The error message was:
We have detected a problem with some tables in the database. Please contact WPML support to get this fixed.
User '***' has exceeded the 'max_questions' resource (current value: 40000)
Array
(
[language] => en
[context] => WP Endpoints
[gettext_context] =>
[domain_name_context_md5] => ***
[name] => wc/file/transient
[value] => wc/file/transient
[status] => 0
[translation_priority] => optional
[allow_empty_value] =>
)
I deleted the message and it didn't show up since, but regularly my admin page goes to the wordpress install.php page because it thinks wordpress is not installed, after a few minute I can connect to my admin space again but a few minutres after, the admin space is blocked again.
Symptoms:
The admin page sometimes redirects to the WordPress install.php page, thinking WordPress is not installed. After a few minutes, I can reconnect, but the admin space becomes blocked again. The error message was: 'User '***' has exceeded the 'max_questions' resource (current value: 40000)'.
I used Query monitor on my home page and there is 130 requests from wpml...
Questions:
How can I fix the issue with too many SQL requests from WPML?
How can I prevent my admin space from being blocked?
Also, increase *WP Memory Limit* to *256* or *512* (the minimum required memory limit for WPML is *128*). Please check the following links for more details
Thank you for the updates. Are you still getting the following warning? Please confirm.
User '***' has exceeded the 'max_questions' resource (current value: 40000)
Please share the WordPress debug.log (not WPML debug information) with us so we can collect more details on this. Refer to the following pages for instructions
To enable WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me with that link, it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion.)
