[Resolved] Some fields do not get into WPML editor
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where some customized fields are not appearing in the WPML editor for translation. This problem is possibly related to the field size limitation in the database. Solution: We recommend increasing the field size in the database to accommodate larger data. You can do this by executing the following SQL command:
ALTER TABLE `wp_icl_translate`<br />CHANGE `field_type` `field_type` varchar(264) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `timestamp`;
Please ensure to replace `wp_icl_translate` with your actual table prefix and make a backup before applying this change. After updating the database, make a minor edit to the main language page to resynchronize the content.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
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.
Background of the issue:
I am working with customized fields on our website and have encountered an issue where some fields are not appearing in the WPML editor for translation. I have provided links to screenshots and the console error that might be related to the issue. Here are the relevant links: hidden link, hidden link, hidden link, hidden link, hidden link, hidden link
Symptoms:
Some customized fields are not visible in the WPML editor. There is a console error related to the WPML plugin at hidden link. The field structure is deeply nested and the field length is 288 characters.
Questions:
Can you check if the console error at hidden link is likely causing the issue with fields not appearing in the WPML editor?
Is it possible that the deep nesting or the length of the field structure is causing the fields to not appear in the WPML editor?
I apologize for the delay in response due to the weekends. Could you please recheck your credentials? I'm getting "Fehler: Der Benutzername wpmlsupport ist auf dieser Website nicht registriert. Falls Sie über Ihren Benutzernamen unsicher sind, versuchen Sie es stattdessen mit Ihrer E-Mail-Adresse.". It was working last week when I tested it.
Upon reviewing your website, I've encountered difficulty troubleshooting the issue because the field you're referring to is nested deeply within some field groups.
Could you please try replicating the issue on our sandbox site here: hidden link so that we can swiftly identify the problem and work towards a solution? I've installed the ACF plugin for your convenience.
As far as we can see, settings have not been copied to another language although it should (when we translate the post): hidden link
Could your team please check why it happens?
As for the 2nd issue (my initial request with missing fields in WPML editor) - we'll replicate structure shortly, it require us some time to build everything for you to show.
I can see the issue now. Please allow me to escalate this to our 2nd Tier Support for further investigation. I will get back to you once I've feedback.
I've received feedback from our 2nd Tier Support team, and here's what they suggested:
We have a workaround to address this issue by increasing the field size using the following SQL command:
ALTER TABLE `wp_icl_translate`
CHANGE `field_type` `field_type` varchar(264) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `timestamp`;
Please remember to adjust the table prefix to match your WordPress installation prefix. Also, it's important to advise making a backup before proceeding with this change.
After making this adjustment, the task should be completed and re-sent for translation, preferably after making a minor change to ensure everything functions correctly.
Alternatively, you can translate normally and then make edits using the Native Editor as a workaround.
I've updated the database on my sandbox site and made minor edits to the main page title at this link: hidden link
As seen in the attached screenshot, the custom field (test caption) is now available for translation. Have you made any minor edits to your main language page? This step is necessary for content resynchronization.
