[Resolved] not able to change the translation preferences
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is unable to save changes to the translation preferences for posts and taxonomies in the WPML settings. After attempting to save, the settings revert to their previous state. Solution: We were unable to replicate the issue on a local copy of the client's site. We can edit and save any translation preference setting in WPML > Settings without any problems. Since the issue appears to be specific to the client's server, we recommend that you provide us with access so we can investigate the issue further. The solution here was server related: Set the value for “max_allowed_packet” configuration from 1M to 64M in the “my.ini” file. Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If none of these steps resolve the issue, please open a new support ticket with us.
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.
Hello, my problem is that I am not able to change the translation preferences of my posts and taxonomies. If I go to “WPML → Settings” and scroll down to the radio buttons that let me change between “Translatable, only show translated items”, “Translatable, use translation if available or fallback to default language” and “Not translatable”, my changes don’t get saved after I press the “Save” button. After the automatic page load, all settings are as they were before the change.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
I am writing to you to let you know that I requested access to your Google Drive to download the site package.
To save time on this matter, I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Hello Andreas, thank you for taking over the task. I granted you access to the archive today at 08:00 UTC.
Thank you also for offering your help by accessing our live site. However, I am limited to providing the Duplicator archive, since our staging site is only accessible from our company’s intranet, and I am not allowed to provide you access to our live site for security reasons. I hope that we can find a solution using Duplicator.
I want to tell you that I was able to resolve the issue.
First I realized that not only the translation options for posts/taxonomies/fields, but any WPML settings in general were not being saved in the first place.
Using the WP debug tool, I was able to fund out that the reason was that the database entry for the WPML settings grew too large for my MySQL server to handle. This could be resolved by changing the “max_allowed_packet” configuration from 1M to 64M in the “my.ini” file.
Thank you very much for your cooperation and your support.
