Problem: You are experiencing a performance issue on your WordPress site using WPML and ACF (Flexible Content + Repeaters), where the option
icl_sitepress_settings
has grown to an unusually large size, primarily due to massive duplication in translation-management custom fields and terms.
Solution: 1) Update the ACF and ACFML plugins to their latest versions to ensure optimal performance and compatibility. 2) Review all ACF field groups to ensure they are properly configured. Remove unused fields or groups, ensure field names are unique within each group, and adjust translation preferences to 'Same fields across languages' where applicable. 3) Consider using a GitHub plugin to clean up the
icl_sitepress_settings
option in the database. This can be tested on a staging copy of your site. However, please be aware that we are not the authors of this plugin and cannot guarantee its behavior.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, 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 necessary, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing a PHP fatal error in your WordPress admin when editing content that uses ACF Pro Flexible Content fields, particularly after updating the ACF Pro plugin, this might be due to ACFML interacting with ACF fields. The error typically occurs during Flexible Content value loading and is more prevalent in translated languages than in the original language.
After adjusting these settings, try making a small change on the German Options page and save it, then save the secondary language options pages. If the problem persists, it might be due to a more complex issue such as leftover data from a Flexible Content field that no longer exists.
Please note that this solution might become irrelevant due to updates or specific configurations in your setup. If these steps do not resolve your issue, or if you find the information outdated, 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 necessary, feel free to open a new support ticket at WPML support forum for further assistance.
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.
