Background of the issue:
I am trying to resolve an issue related to the 'Large DP autoload installer settings' in WPML. I am using this forum thread as a reference: https://wpml.org/forums/topic/wp_installer_settingsis-autoload-and-large/?paged=3. We need an urgent update on this ticket to avoid moving our 11 paying clients to another platform. The issue can be seen on this page: hidden link.
Symptoms:
The client did not specify the exact symptoms or errors they are experiencing, but they implied there is a critical issue with the 'Large DP autoload installer settings' that requires urgent attention.
Questions:
What is the status of the ticket related to the 'Large DP autoload installer settings'?
What steps can be taken to resolve the issue with the 'Large DP autoload installer settings'?
Thanks for reaching out and for sharing the previous support thread, that should help us narrow down the issue. To make sure we’re dealing with the same problem, could you please provide a bit more detail about the errors your client is encountering?
Also, to assist you more efficiently, please share the following:
1. The size of these database keys
- wp_installer_settings
- icl_sitepress_settings
- icl_st_settings
2. Please attach the site's debug information, so we can rule out any misconfiguration. - Go to WPML > Support > Debug Information
- Copy the debug info displayed there
- Paste it into the private field I’ve enabled below
More info: https://wpml.org/faq/provide-debug-information-faster-support/
Thanks for your response. I have attached the debug information as requested, and have included the database key sizes below:
wp_installer_settings: 122,1 kb (too big)
icl_sitepress_settings: 18,27 kb (close to acceptable, but larger than the official WP recommendation of 5-10 kb)
icl_st_settings: 463 bytes (perfect!)
Please note that these numbers are from our own agency site. We have multiple clients affected by the same issue, where the largest key size for the wp_installer_settings key is above 600 kb (ecom site).
Please do not hesitate to give us a shout if you need anything, but please keep in mind that we as an agency are bound both by GDPR and client agreements.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Please kindly note that our developers are aware of those issues and they are planning on fixing those problems in a future version of WPML.
For now, we do sadly not have a workaround for this issue, but this week another client reported that he used the following repo to solve the issue: hidden link
If you make use of this repo, please make sure to first take a backup of your site, including the database.
Thanks for your note. Your comment about "in a future version" just cements our, and our clients view on WPML. This is clearly no longer a serious and well-maintained plugin.
Unless you can give us a release schedule, we will terminate our own and all clients licenses, and do a press release on why we have chosen to move away from WPML as this case deserves to be seen by the public domain.
Until further notice; we recommend anyone reading this ticket (we will ensure this ticket is posted elsewhere as well) to STAY AWAY from WPML.
Kind regards,
Roy Edvard Ellingsen
Managing Director
Venturis - Norway, Sweden, Denmark
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I would like to offer to investigate this issue further, measure the performance impact, and try to find a workaround for the issue.
To do this, I will need temporary access (wp-admin and FTP) to the website or a site package that includes at least the wp-content folder and a database dump file. Anyhow, when it comes to measuring performance, it would be ideal to have a complete site package including uploads.
You can find the required fields below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "Duplicator PRO" to create a copy of the website so I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or a copy of the website from your server for this purpose.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
