Problem: You are experiencing issues with importing XLIFF files for translation on a site that has recently switched from Polylang Pro to WPML. The import fails for two of the pages, and you suspect it might be related to a plugin conflict. Solution: We recommend temporarily deactivating the YoastSEO plugin and its Pro version, then attempting the XLIFF import again. Ensure you perform a full website backup before making these changes. If the problem persists or occurs with other XLIFF imports, please contact us for further assistance.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue continues, do not hesitate to open a new support ticket.
Problem: If you're experiencing issues with incorrect repeater field labels in confirmation emails when using WPForms with the WPForms Multilingual plugin, such as seeing labels like 'Field ID #6_2' instead of the correct form labels. Solution: We recommend following these steps to resolve the issue: 1. Ensure you back up your site for safety. 2. Navigate to
This change should correct the label display in your confirmation emails. Please try this solution and let us know the results.
If this solution does not apply to your case, or if it seems 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to optimize their database, which has grown significantly due to numerous entries in the posts_meta table. They reported that WPML Delete Jobs did not effectively reduce the database size. Solution: We analyzed the database and found that the _postsmeta table was indeed the largest. We also discovered a large number of attachment entries that might be bloating the database. We recommend creating a staging version of the website and running the following SQL queries to clean up unnecessary entries:
SELECT p.ID FROM `93lzr5_posts` p LEFT JOIN `93lzr5_icl_translations` t ON p.ID = t.element_id WHERE p.post_type = 'attachment' AND t.element_id IS NULL;
DELETE pm FROM `93lzr5_postmeta` pm WHERE pm.post_id IN (SELECT p.ID FROM `93lzr5_posts` p LEFT JOIN `93lzr5_icl_translations` t ON p.ID = t.element_id WHERE p.post_type = 'attachment' AND t.element_id IS NULL);
DELETE p FROM `93lzr5_posts` p LEFT JOIN `93lzr5_icl_translations` t ON p.ID = t.element_id WHERE p.post_type = 'attachment' AND t.element_id IS NULL;
Please ensure to perform these actions on a staging site and not on the live site. If this solution does not apply or is outdated, we 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 further assistance is needed, please open a new support ticket.
Problem: If you're experiencing a fatal error with the message 'Declaration of MonologLogger::emergency(Stringable|string $message, array $context = []): void must be compatible with PsrLogLoggerInterface::emergency($message, array $context = [])', this is due to a compatibility issue in the code. Solution: We recommend updating to WPML version 4.7.1, which is expected to resolve this issue. The update should be available in approximately 1-2 weeks. If you encounter this issue before the update is released, you might find a temporary workaround on the Roots forum: Roots forum discussion.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 open a new support ticket at WPML support forum for further assistance.
Problem: The client wants the button text to be translatable and the link to automatically adjust to the translated version of the page. They are unsure which translation preference to use for achieving this functionality. Solution: We recommend using the following approaches: 1. Set the translation preference to 'Translate' and use the Advanced Translation Editor to translate the URL. For detailed guidance, refer to how to translate URLs using the Advanced Translation Editor. 2. If you choose to use 'Copy Once', you can manually translate the button text and URL using the WordPress editor. However, for automatic URL adjustments and button text translations, using the 'Translate' option with the Advanced Translation Editor is the best approach. Additionally, you can follow the discussion and solutions provided in this forum thread: WPML filter hook for ACF fields link translations.
If this solution does not resolve your issue or seems 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. Should you need further assistance, please open a new support ticket.
