sanderv-27
|
Hello,
thank you for the update.
What is the timeline for this?
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
While I can’t provide an exact timeline, I can confirm that this feature is planned for the next major WPML release. That said, please keep in mind that release schedules can shift depending on development priorities, so this is more of an estimate than a fixed timeline.
We will update this ticket as soon as there are news.
|
sanderv-27
|
Hello,
it seems a new update rolled out today. After install the database remains the same, but perhaps it would take some time. Did this update indeed resolve these issues, as promised in earlier tickets?
So far I am still seeing unacceptable large autoload database files related to WPML.
edit: turns out the problem has gotten even worse, with the file sizes even growing!
at start of ticket:
1 wp_installer_settings yes 105736
3 icl_sitepress_settings yes 34717
4 icl_st_settings yes 20869
current:
1 wp_installer_settings yes 111828
3 icl_sitepress_settings yes 34782
4 icl_st_settings yes 21183
|
peterL-60
|
Our hosting provider informed us today that our autoload has grown too large and due to the large size object cache is not able to function. Obviously causing performance issues.
All of the biggest autoloaded options are from WPML, including the 'wp_installer_settings' I see being discussed here. This option is base_64 encoded, gzipped, and serialized. But I decompressed it to view what this content is that needs to be loaded on every single page request.
To my surprise, it is a ton of plugin repository meta, like different WPML package information. And primarily a TON of change log data from previous versions of WPML. I can/could change this file to not autoload, but it doesn't really matter what I do because WPML is calling this option with every single page request, so autoloaded or not it is going to get called.
It would be overly aggressive to call this on every admin page, but calling it on every frontend request is nuts.
icl_sitepress_settings is an even bigger issue on our site as we have many custom ACF fields in repeaters and flexible content rows, all stored inappropriately in the icl_sitepress_settings option. We reported that issue around two years ago now and a resolution has been "in development."
|
peterL-60
|
Looking more closely at the data in wp_installer_settings I see metadata including change logs and release notes (which often are a carbon copy of the change log) of 30 different plugins/'toolsets'. Without the gzipping it is nearly a half of megabyte of plugin metadata.
The fact that it was gzipped would seem to imply that someone realized at some point this was a TON of data to be storing in a WordPress option. But maybe lacked the understanding that storing all of this in an option and requesting it on every page load was going to cause a lot of performance issues for people, gzipped or not, autoloaded or not.
I've submitted bug reports in the past finding other WPML options autoloading with 300kb of data. This sort of thing has been a reoccurring issue over the years we've used WPML. I really feel WPML needs to put some big emphasis on performance best practices and make it someones job specifically to oversee and manage performance issues in this plugin. We do our best to report things when we see them. We always hear it is being worked on but so far it has been years with no resolutions.
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
This current release did not include the fix for the issue you are experiencing in this ticket.
The development ticket is still open and scheduled for one of the upcoming releases.
|
sanderv-27
|
oh, so it is not the next update, but simply ' a future release'... Nice way to keep things vague.
Also, could you explain why these database entries are still growing in size?
wp_installer_settings would indicate installer settings, not a constant updated table?
|
Bobby
WPML Supporter since 04/2015
Languages:
English (English )
Timezone:
America/Los_Angeles (GMT-07:00)
|
We appreciate your patience in this matter, however, as I have mentioned I dont have a date on when this will be released. It is in the schedule for our next major release.
Once it is released you will be updated directly in this ticket.
I don't have an answer but will direct your question to the developers assigned to this issue.
|
eugeneM-7
|
Hello!
@Bobby, I joined this thread due to the same problem. Hence, I'm interested to get notified about the fix as well.
The autoload size list of one of my websites (as you can see `wp_installer_settings` is on top of it):
1. wp_installer_settings yes 110400
2. _icl_cache auto 65937
4. icl_st_settings yes 47929
6. icl_sitepress_settings yes 16376
11. wpml_strings_need_links_fixed yes 10795
12. wpml_shortcode_list on 10268
14. otgs-installer-log yes 9747
16. wpml_disabled_switcher_template_objects auto 7145
Thank you!
|
rodrigoM-14
|
HI,
We're having the same problem on several websites. We need a solution as soon as possible because it's becoming virtually impossible to work with WordPress.
Thank you.
Best Regards
|
mateuszG-14
|
Hi,
same problem. Has anyone found a solution yet or know when the WPML team will fix this?
Best,
Mateusz
|
JP
|
Hi, I am facing the same problem. My site goes down at this moment when I activate WPML due to the huge autoload scipt. Please inform me also how to solve this?
JP
|
adamZ-10
|
Hello,
I experience the same problem - the size of the option is significantly uncomparable with the others, looking forward to mark this issue as the one with the higher priority
Kind regards,
Adam
|
pierre-yvesm
|
Hello,
Same problem here. When is an update going to be put in place to fix this big problem?
Kind regards,
PY
|
