Problem: You are experiencing a fatal error when saving or editing a translation page in WordPress, where WPML's hook crashes due to expecting a WP_Post object but receives null. This issue persists even after updating to WPML 4.9.2. Solution: We have investigated the issue and found that it appears to be specific to your hosting environment rather than a bug in WPML itself. We recommend contacting your hosting provider to ensure that the REST API is not blocked and to temporarily disable any restrictive security layers that might be interfering with the save process. Additionally, consider whitelisting WPML-related requests from these protections. If the problem continues, you might need to consider changing your server. For more details on REST API dependencies, please visit https://wpml.org/documentation/support/rest-api-dependencies/.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 needed, please open a new support ticket for further assistance.
Problem: You have updated a page in French and deleted its English translation to start over. However, when trying to add a new translation by clicking the + button, instead of being redirected to the bilingual Translation board, you are taken to a new WordPress page to recreate the English page from scratch. Solution: If you recently migrated your site using the All-in-One WP Migration plugin, this might be a known issue. We recommend following the workaround described here: https://wpml.org/errata/all-in-one-wp-migration-database-error-missing-uuid-column-after-migration/ If this is not the case, please enable debugging to identify any specific errors related to WPML: 1. Edit your wp-config.php file to enable WordPress debugging with these lines before the comment /* That's all, stop editing! Happy publishing. */:
2. Replicate the error. 3. Check the debug.log file in the /wp-content directory for any WPML-related errors. 4. Share the full error message with us for further assistance.
If the solution provided here becomes irrelevant due to updates or does not apply 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 at WPML support forum.
Problem: You are experiencing an issue where clicking the '+' icon to manually translate pages redirects you to the Translation Queue, but no content appears, preventing you from proceeding with translations. Solution: We have identified that you are using the All-in-One WP Migration plugin, which might be causing this issue. This is a known problem related to the plugin. We recommend following the workaround described in the errata here: https://wpml.org/errata/all-in-one-wp-migration-database-error-missing-uuid-column-after-migration/.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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.
Problem: You are experiencing a critical error during WPForms submission when the WPForms Multilingual plugin is active. This issue occurs even before translating the form. Solution: We recommend trying the solution provided in the WPML errata for issues related to WPForms. You can find the specific guidance here: WPForms Incorrect Field Labels and Email Notification Issue with Repeater Fields.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: You are encountering a database error on your WordPress site indicating that the table 'wp_icl_translate_job' is missing. This error is triggered by the WPML Translation Management plugin when making a REST API request to fetch credits in progress, and it appears only on a specific page. Solution: If you're experiencing this issue, we recommend you try the following steps to safely recreate the missing table without risking any data loss: 1. Ensure you create a full backup of your site and database to prevent any potential data loss. 2. Follow the detailed instructions provided in our errata to recreate the missing tables: https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket for further assistance.
Problem: The client is experiencing an issue where an error message prompts to activate the WPML String Translation plugin despite it already being active. Additionally, there is broken HTML in the language switcher column on the 'Pages' screen in the WordPress admin. Solution: We recommend checking if there are any conflicts with other plugins or themes that might be causing this issue. You can do this by temporarily deactivating other plugins and switching to a default theme to see if the problem persists. If the issue is resolved, reactivate them one by one to identify the culprit. If the problem continues, please provide temporary access (admin account and/or staging environment) for further inspection.
Please note that the solution provided might be 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, do not hesitate to open a new support ticket for personalized assistance. You can do so here: https://wpml.org/forums/forum/english-support/
Problem: You are unable to translate some Divi Pixel modules, specifically the Tile Scroll content and Price Table content on your "Cenote Diving" page using WPML with Divi 5 and the latest version of Divi Pixel. Solution: We recommend checking if this issue is related to a known compatibility problem with Divi Pixel and Divi 5 modules. Please visit the following link for a potential workaround: https://wpml.org/errata/divi-pixel-new-divi-5-modules-are-not-translatable/
If this solution does not resolve your issue or seems outdated, we highly recommend opening a new support ticket. Also, ensure you have the latest versions of your themes and plugins installed. For further assistance, please check related known issues at https://wpml.org/known-issues/ and consider contacting us directly through our support forum.
Problem: If you're experiencing a fatal error when trying to update/save on an ACF options page, which results in a TypeError because an array is given instead of a string, this might be due to an issue with nested options fields in secondary languages. Solution: We recommend trying the workaround provided in the WPML errata. Please ensure to back up your site before making any changes. You can find the detailed steps here: Advanced Custom Fields: Fatal Error when saving nested options fields in secondary languages.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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.
Problem: If you're experiencing an issue where the language switcher widget disappears when you navigate to the translated version of your site, it might be due to the Header template not being translated. Solution: We recommend translating the Header template. You can do this by navigating to WPML > Translation Dashboard and ensuring the Header template is fully translated. This should resolve the issue and make the language switcher visible on your translated site.
Please note that this solution might be 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 problem persists, please open a new support ticket.
Problem: If you've installed the OTGS installer and the WPML plugin, but the setup page appears blank and the configuration doesn't start, this might indicate a specific issue with your website or server environment rather than a general WPML problem. Solution: We recommend checking if other core WordPress functionalities, such as the WordPress Site Health > Info page, are also failing to load. If they are, it suggests that the problem lies with a core WordPress function, specifically
got_url_rewrite()
, which WPML also relies on. This issue is likely specific to your server or environment. Please contact your hosting provider to resolve any underlying issues with this function. Once resolved, try loading the WPML setup page again. If the problem persists, 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 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 continues, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues updating translations due to an error with Object Cache Pro. Solution: We recommend using the native WordPress function wp_cache_add_non_persistent_groups to exclude groups from object caching.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an MD5 error when saving ACF field groups in non-primary languages, particularly with nested fields such as a group containing a sub-field, this might be due to a bug in ACFML versions 2.2.2 and 2.2.1. Solution: We recommend applying a temporary workaround until a permanent fix is available. Please edit the file
This adjustment should prevent the error from occurring when saving in secondary languages.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
