Skip Navigation

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.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: 

This topic contains 13 replies, has 2 voices.

Last updated by Dražen Duvnjak 8 months, 3 weeks ago.

Assisted by: Dražen Duvnjak.

Author Posts
February 13, 2024 at 8:21 am #15295839

coinQ

Okay. We already tested the two suggested scenarios with the custom theme and all the plugins. Sometimes it shows an update failed error, mostly on large pages that have already been translated into other languages. 

Regarding the autoload data, what will we do then? When we contacted the WP Engine support team, they had a limit on the autoloader data, which is 800 kb, and ours is more than 1.2 Mb. They also told us this would be the main issue with slowness. When we checked with the WP engine, they said there was no option to change the limit, and they asked us to contact the plugin team. So we contacted the WPML team, and they said they need these options to be loaded automatically, and if we turn them off, the WPML plugin won't work. What will we do then? How can we fix this autoload issue?

February 13, 2024 at 8:22 am #15295857

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

can you please check what tables have issues with autoload data and size and let me know?

Thanks,
Drazen

February 13, 2024 at 8:25 am #15295867

coinQ

Top largest autoload rows:
mysql> SELECT LENGTH(option_value),option_name FROM wp_options WHERE autoload='yes' ORDER BY length(option_value) DESC LIMIT 20;

+----------------------+-----------------------------------------+
| LENGTH(option_value) | option_name |
+----------------------+-----------------------------------------+
| 735136 | wpml_strings_need_links_fixed |
| 110647 | ATE_RETURNED_JOBS_QUEUE |
| 87763 | rewrite_rules |
| 66422 | wpseo_taxonomy_meta |
| 17916 | icl_sitepress_settings |
| 17081 | wp_user_roles |
| 15572 | jetpack_active_plan |
| 15222 | wpseo_titles |
| 12152 | cron |
| 10204 | wpseo-premium-redirects-export-plain |
| 9747 | otgs-installer-log |
| 8168 | fs_accounts |
| 7599 | wpml_shortcode_list |
| 7004 | advanced_ads_adsense_report_domain |
| 6803 | wpml_language_switcher_template_objects |
| 5662 | wpseo |
| 5592 | two_settings |
| 5346 | otgs_active_components |
| 5331 | wpcf-custom-taxonomies |
| 5285 | jetpack_plugin_api_action_links |
+----------------------+-----------------------------------------+

Total autoloaded data (in bytes):
mysql> SELECT SUM(LENGTH(option_value)) FROM wp_options WHERE autoload = 'yes';

1268285
We want that total to be under 800k or so for good performance.
This is ~468285 bytes larger than 800k... Not ideal.

February 13, 2024 at 2:51 pm #15298171

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

thanks for getting back.

Not all shared tables are related to WPML, only one that has WPML, icl or ate in their name.

Anyway let's start with the first one and the largest:

wpml_strings_need_link_fixed - Go to WPML > Settings > Run Translate link target tools.

Let me know if that helps.

Regards,
Drazen

February 21, 2024 at 8:14 am #15325712

coinQ

Hello,

The task is stopped when the system goes to sleep. We have more than 100,000 links on posts, and that may take a lot of time to complete.

Are there any other solutions? Please let us know.

Thank you

February 21, 2024 at 11:29 am #15327400

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

you try to empty it or remove the option but test it first on staging or after the backup.

For the icl_sitepress_settings option, you can keep it to be not autoloader, and the same for ATE_RETURNED_JOBS_QUEUE and otgs-installer-log.

Please check next for more info:
- https://wpml.org/forums/topic/wpml_strings_need_links_fixed-entries-in-wp_options/#post-12048565
- https://wpml.org/forums/topic/wpml_strings_need_links_fixed-entries-in-wp_options/page/2/#post-12077399

I think that should help with WPML-related keys, and for others that are larger and not related to WPML, I suggest checking with other plugin authors.

Hope this helps.

Regards,
Drazen

February 23, 2024 at 11:24 am #15337287

coinQ

Hello,

Thank you for the response

So it is okay to disable the autoload for the below options

icl_sitepress_settings
ATE_RETURNED_JOBS_QUEUE
otgs-installer-log
otgs_active_components

right? Can we proceed with that? Are you sure that won't lead to any issues in the future? If you can give a confirmation, we can make the changes ASAP.

Please let me know

Thank you

February 23, 2024 at 11:47 am #15337419

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

I am not sure for the last one: otgs_active_components

Let me get one more confirmation for each from our 2nd tiers and I will get back to you soon.

Regards,
Drazen

February 23, 2024 at 12:12 pm #15337533

coinQ

Hello,

Thank you; that would be helpful. We only need to make sure that in the future the plugin works properly without any issues after we disable autoload options for the mentioned tables. Also, please ask them to list out the database options that we can set its autoload to "no" from the WPML plugin.

Thank again

February 23, 2024 at 3:07 pm #15338427

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

I have checked and this is the current status and explanation:

autoload = no, fire SQL each time, autoload = yes save the data in PHP memory and loads on the first page

icl_sitepress_settings should not be removed from the autoload as this is frequently used everywhere in the WPML and add-ons and will call SQL queries too many times then

otgs-installer-log can be removed from autoload since it is just logs.

About others, we suggest testing first if it affects your website in any way, but if you see improvement after the changes and setting autoload to NO then autoload should not affect the functionality. To be honest we are also working on this case and going over each option making improvements and making sure they need to be autoloaded or not. I will update you when I have more news, but this process will take time and I am afraid this is the best we can suggest for you now.

Hope this makes sense, let me know how it goes and if you have any other questions.

Drazen

February 27, 2024 at 11:32 am #15348829

coinQ

Hello,

Thank you for the response.

Okay, we will remove "otgs-installer-log" from the autoload. We will check the other 2 remaining options (ATE_RETURNED_JOBS_QUEUE, otgs_active_components). Since we are not aware of how these options are working with WPML, it is a risky task to disable these unknown options from autoload. Please check it on your side too, because you have more knowledge of the mentioned options and how they are connected with WPML.

I am happy to hear that you guys are working to improve the database. Please do it ASAP, because many people face this same autoload issue on their website too. Almost all the highly loaded options are from the WPML plugin. It would be great if you could find a solution and fix this autoload issue as soon as possible.

Thank you

February 27, 2024 at 2:37 pm #15349613

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

thanks, as said setting those two also to autoload NO, should not cause any concern in the functionality of WPML, the difference would be in SQL queries only, which then can also affect your performance / load.

I suggested you test this, since I can not be 100% sure, as this is being still tested and debugged from our side what is the best approach here.

I understand your concern and we are working on this, but this won't be very soon and will take some time. For now it is scheduled for WPML 4.7. I will update you when I have more news.

Regards,
Drazen

March 6, 2024 at 10:35 am #15378451

coinQ

This thread is marked as fixed in the next release.

Is it true? Can we expect the fix in the next release?

March 7, 2024 at 10:04 am #15383141

Dražen Duvnjak
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

It is currently planed for WPML 4.7, but I can not guarantee if there might be some smaller bug fix version before.

I will update you on any news.

Regards,
Drazen