Problem: You are using the Advanced Translation Editor (ATE) to translate content, but your ACF fields are missing when you access ATE. Solution: 1. Check the configuration of your ACF Field Groups in your posts. If they are set to "Expert", you need to configure each field individually. 2. We recommend setting the field groups to "Same fields across languages" to automatically configure all fields appropriately. Alternatively, follow the guide on setting up ACF fields with WPML: Recommended Custom Fields Translation Preferences for ACF and WPML. 3. Ensure that fields such as Flexible Content and Repeater are set to "Copy", and all text fields are set to "Translate". 4. After adjusting these settings, edit any field on the original content, save the post, and then attempt to translate it again.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please open a new support ticket. We also 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. For further assistance, visit our support forum: WPML Support Forum.
Problem: If you're experiencing an issue where the search input field on an ACF relationship field is disabled in translated posts, this might be due to a change introduced in version 2.1.0 of the Advanced Custom Fields Multilingual (ACFML) plugin. This problem persists in version 2.1.3. Solution: We recommend modifying a line of code in the ACFML plugin. In the file
This change might resolve the issue. However, please note that this solution could become outdated or might not apply 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 the problem persists, please open a new support ticket.
Problem: You are encountering a deprecated error and headers already sent issue on your login page when debug mode is enabled in a WPML environment. The specific error message is: 'Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/wp-includes/class-wp-user.php on line 216'. This is followed by a failure to load the page due to 'Cannot modify header information - headers already sent by ...'. Solution: We recommend updating your WPML to the latest version as this issue should be resolved in that update. Before updating, ensure to back up your site. If this solution does not apply because it is outdated or not relevant to your 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 issues persist, please open a new support ticket.
Problem: The client reported significant slowdowns on their staging site after installing WPML, with page load times increasing to 6-10 seconds. This issue was not present on a similarly configured site without WPML. The client tried various optimizations, including disabling WPML SEO and WPML String Translation modules, which improved load times.
Solution: We recommended migrating the site to our Cloudways testing environment to isolate the problem. The client used the Cloudways WordPress Migrator plugin for this purpose. After migration, we discovered that the combination of Admin Columns Pro, ACF, and ACFML plugins significantly impacted performance. We provided a temporary workaround by modifying the
translateField
method in the ACFML plugin to prevent certain processes from executing in the admin area, which improved backend performance. We also advised on general performance enhancements such as using PHP 8, enabling caching, and optimizing database indexes.
Please note that this solution might not be relevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing a deprecated warning with
Deprecated: str_contains(): Passing null to parameter #1 ($haystack) of type string is deprecated
when using WPML with PHP 8.2. The issue seems related to a compatibility problem between LearnDash and WPML. Solution: We recommend reproducing the issue on a clean staging site with only WPML and LearnDash LMS activated. If the issue persists, follow these steps: 1. Backup your site. 2. Switch to a default WordPress theme temporarily. 3. Deactivate all unrelated plugins. 4. Check if the issue still exists. 5. Reactivate plugins in groups to identify the problematic one. 6. Switch back to your original theme. If you identify the plugin causing the issue, you can apply a temporary patch provided by the client. Additionally, our developers are aware of this issue with PHP 8.2 and are working on a fix expected in WPML version 4.7. Meanwhile, to avoid displaying errors to site visitors, disable debug mode by adding
define('WP_DEBUG_DISPLAY', false);
to your wp-config.php file. For more details on related issues, please visit this errata page.
If this solution does not resolve your issue or seems irrelevant, we highly recommend checking related 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.
Problem: You are experiencing a styling issue in the backend when using the Gravity Forms Multilingual addon, resulting in a broken UI. Solution: We recommend disabling the No Conflict mode in your Gravity Forms settings. This mode, when enabled, prevents third-party scripts from affecting the Gravity Forms administration pages, which can lead to styling conflicts. To disable it, edit your form settings and turn off the No Conflict mode. For more detailed instructions, visit the Gravity Forms documentation: https://docs.gravityforms.com/enabling-no-conflict-mode/
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
