Home›Support›English Support›[Resolved] URGENT! icl_sitepress_settings is 510803 in length causing website down-time
[Resolved] URGENT! icl_sitepress_settings is 510803 in length causing website down-time
This thread is resolved. Here is a description of the problem and solution.
Problem:
How to reduce the size of WPML database tables?
Solution:
Please, back up everything before proceeding. And test the following on a staging area first.
For the icl_sitepress_settings option, you can keep it to be not autoloaded. Furthermore, you can reduce the wp_options table size by following these steps:
These option names have high amount of data and here's how you can reduce it:
- wpml_notices: can be deleted
- wpml_strings_need_link_fixed: can be reduced by running the Translate Link Targets option under WPML β Settings.
- _wpml_tp_api_logger: can be deleted
- WPML(logs) can be deleted
- wpml_tp_com_logs can be cleared from WPML > Support > communication log
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
I understand that your hosting company informed you that some WPML data in the website's database are causing problems.
The data you mentioned are required for WPML to work correctly. With that said, our developers are already working on a solution to not autoload everything.
I will link this ticket to our developer's one and update you once I have news. Please note this will probably take a while; thanks for your patience.
Hi Ahmed, yesterday before you responded I changed icl_site_settings to not be autoloaded and the website continued functioning correctly and our CPU usage dropped to a healthy level. I noticed that we also have an icl_st_settings that I left as autoloaded as well as WPML(TM), wpml-tm-custom-xml, and WPML(ST-MO). I left all of those as autoloaded. What issues could occur from changing icl_site_settings to not be autoloaded? This issue needs to be escalated with your team since our very expensive hosting plan on WP Engine cannot handle the massive amount of autoloaded data coming from WPML.
Do you have an ETA on when WPML will have a solution to not autoload everything as Ahmed mentioned above? We cannot afford to have our website going down because of a massive amount of autoloaded data from WPML causing 502 errors on WP Engine. Our primary issue is the icl_sitepress_settings size. I've moved the XML config out of the database and that helped a little, but not much. We may need to look into an WPML alternative if this autoloaded data issue can't be resolved soon. Thank you!
Hi Ahmed, I tried to copy the current website to our staging environment but the copy process is failing due to some fatal error related to WPML. Wp Engine said the copy was failing at the search and replace and that they did some testing on the staging site and when running a search and replace they are getting an error related to the WPML plugin.
PHP Fatal error: Uncaught Error: Class "WP_Upgrader_Skin" not found in /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-installer-upgrader-skins.php:3
Stack trace:
#0 /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-otgs-installer-autoloader.php(18): include()
#1 [internal function]: OTGS_Installer_Autoloader->autoload()
#2 hidden link): unserialize()
#3 hidden link): WP_CLI\SearchReplacer->run_recursively()
#4 hidden link): WP_CLI\SearchReplacer->run()
#5 hidden link): Search_Replace_Command->php_handle_col()
#6 [internal function]: Search_Replace_Command->__invoke()
#7 hidden link): call_user_func()
#8 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
#9 hidden link): call_user_func()
#10 hidden link): WP_CLI\Dispatcher\Subcommand->invoke()
#11 hidden link): WP_CLI\Runner->run_command()
#12 hidden link): WP_CLI\Runner->run_command_and_exit()
#13 hidden link): WP_CLI\Runner->start()
#14 hidden link): WP_CLI\Bootstrap\LaunchRunner->process()
#15 hidden link): WP_CLI\bootstrap()
#16 hidden link): include('...')
#17 /usr/share/wp-cli.phar(4): include('...')
#18 {main}
thrown in /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-installer-upgrader-skins.php on line 3
Fatal error: Uncaught Error: Class "WP_Upgrader_Skin" not found in /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-installer-upgrader-skins.php:3
Stack trace:
#0 /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-otgs-installer-autoloader.php(18): include()
#1 [internal function]: OTGS_Installer_Autoloader->autoload()
#2 hidden link): unserialize()
#3 hidden link): WP_CLI\SearchReplacer->run_recursively()
#4 hidden link): WP_CLI\SearchReplacer->run()
#5 hidden link): Search_Replace_Command->php_handle_col()
#6 [internal function]: Search_Replace_Command->__invoke()
#7 hidden link): call_user_func()
#8 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
#9 hidden link): call_user_func()
#10 hidden link): WP_CLI\Dispatcher\Subcommand->invoke()
#11 hidden link): WP_CLI\Runner->run_command()
#12 hidden link): WP_CLI\Runner->run_command_and_exit()
#13 hidden link): WP_CLI\Runner->start()
#14 hidden link): WP_CLI\Bootstrap\LaunchRunner->process()
#15 hidden link): WP_CLI\bootstrap()
#16 hidden link): include('...')
#17 /usr/share/wp-cli.phar(4): include('...')
#18 {main}
thrown in /nas/content/live/ninjastage1/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/installer/includes/class-installer-upgrader-skins.php on line 3
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
Do you have any insight into why this error might be happening?
The "Class not found" issue is generally caused if the file containing the required class is either missing or not loaded properly.
While I'm not sure how the search and replace process works on WPEngine servers, I can either log in to the production website, install a plugin and do the cloning, or I can setup a website on our servers and let you migrate.
Please let me know how you would like to proceed π
Hi Ahmed, I'm going to give you access to our staging environment, could you please enable a private reply for me to share that access info? Thank you!
I was able to clone the staging area. I wanted to let you know in case you want to delete it.
On the other hand, I checked the database tables locally and I can see that the "icl_sitepress_settings" option is set to not to be autoloaded (check screenshot). Is it the same on the production version of your website?
If that's correct, did you have any issues with your installation so far?
I'm going to escalate this as promised, I'm just collecting some information for our devs.
Hi Ahmed, I did set icl_sitepress_settings to not be autoloaded out of desperation because our website was giving 502 errors until I made that change. Your team had said that it was necessary for it to be autoloaded, but I haven't seen any issues since I made that change. Thank you for escalating this!
I have some news (I will let you decide whether they're good or not π ).
For the icl_sitepress_settings option, you can keep it to be not autoloaded. Furthermore, you can reduce the wp_options table size by following these steps:
Please, back up everything before proceeding. And test the following on a staging area first.
These option names have high amount of data and here's how you can reduce it:
- wpml_notices: can be deleted
- wpml_strings_need_link_fixed: can be reduced by running the Translate Link Targets option under WPML β Settings.
- _wpml_tp_api_logger: can be deleted
- WPML(logs) can be deleted
- wpml_tp_com_logs can be cleared from WPML > Support > communication log
I'll also keep this ticket open and update you when the reported issues are fixed.
