Problem: The client experienced a persistent JavaScript
TypeError: Cannot read properties of undefined (reading 'isTranslated')
when attempting to select WPForms for translation in the WPML Translation Dashboard after changing the site's default language from Polish to English.
Solution: We attempted several troubleshooting steps: 1. Ensured the WPForms Multilingual Addon was active and up to date. 2. Cleared all pending/stuck translation jobs for WPForms and re-attempted translation. 3. Made minor edits to original forms and accessed them on the frontend to trigger string registration. 4. Executed WPML troubleshooting actions such as clearing the plugin cache, removing ghost entries, fixing element_type and charset, re-syncing language info, and taxonomies. 5. Tried selecting WPForms one by one instead of all at once to isolate the issue. Despite these efforts, the error persisted, indicating a deeper systemic issue possibly related to database or WPML-WPForms integration inconsistencies. The ticket was escalated to our 2nd tier of support for further investigation.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: If you're experiencing warnings and a 404 page after using the autotranslate feature on your site, particularly when switching to languages like Danish, and your theme is compatible with WPML, the issue might be related to your site settings. Solution: We discovered that although the Settings → General page displayed values for both Site URL and Home URL, the Home URL was actually empty in the database (in the wp_options table). This mismatch was likely causing the problem. Simply re-saving the settings page might not repopulate the value due to the issue itself preventing it. Therefore, we recommend updating the Home URL directly in the database. After making this change, please check your site to confirm that everything is working as expected.
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 problem persists, please open a new support ticket.
