Problem: If you're experiencing 404 errors with resumes when the Tax Exception plugin for WooCommerce is enabled, and the errors disappear when the plugin is disabled. Solution: We recommend trying to switch the language settings and then adjusting the permalink settings in your WordPress dashboard. After making these changes, save the settings again. This approach helped resolve similar issues in our tests, even with the Tax Exception plugin activated.
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, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client created pricing forms using the WooCommerce plugin and AcoWebs WooCommerce Custom Product Addons plugin. The forms function correctly in the first language, but issues arise with displaying or hiding fields using the Global Attribute in other languages. Solution: We noticed that the missing fields do not have the same settings among languages in the conditional tab. We recommend checking the settings in each language to ensure consistency. Unfortunately, the plugin documentation does not mention the recommended method for translating the conditional tab, and the field in the translated add-on is greyed out, making it unchangeable. We advise contacting the plugin's support team to inquire about the custom field name, which will allow you to set it to either copy once or translate and change it to the translated version. For further guidance, you can refer to the plugin documentation here: Acowebs Plugin Documentation.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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 at WPML Support Forum.
Problem: You are trying to translate a multi-page form from French into German using GravityForms and WPML, but some texts remain in French despite using the string translator and advanced translator. Solution: If you're experiencing this issue, we recommend saving the form again in GravityForms. After saving, the missing translation strings should appear in the advanced translation interface, allowing you to complete the translation process.
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 at WPML support forum for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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: The client is trying to translate user notifications for Gravity Forms using WPML, but despite following the guide and translating all forms and strings, the notifications are still sent in German when the enquiry is made from the English version of the site. Solution: We conducted a test by setting up a local copy of the client's site with only essential plugins activated (WPML CMS, String Translation, Gravity Forms, and Gravity Forms Multilingual) and using the default WordPress theme. We created a test page and did not encounter the issue in this minimal setup. We suggest the client to: 1) Deactivate all non-essential plugins. 2) Switch to the default WordPress theme temporarily. 3) Clear the browser's cache or try accessing the site using a private browsing window to see if the issue persists.
If these steps do not resolve the issue, we 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 continues, please open a new support ticket.
Problem: The client is trying to optimize their website's performance after installing the AAA Option Optimizer plugin. They noticed several items in the autoload option table generated by WPML plugins that are unused but increasing the autoload size. The client is concerned about the impact of WPML plugins on website performance.
Solution: We recommend that disabling autoload for the items listed, which appear to be unused based on the tool's report, should be safe. Although these options are not large and might not significantly impact performance, disabling them could help if they are indeed unnecessary. Any needed options will be loaded on demand via the
get_option
function and cached for the duration of the request. For further performance improvements, we suggest reviewing additional tips on optimizing site performance here.
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 persists, please open a new support ticket.
Problem: The client is experiencing an issue where the .htaccess file on their WordPress site changes periodically, causing the site to break. This requires resaving permalinks to fix the issue. Solution: We have determined that WPML is not the cause of the .htaccess file changes. It is likely due to third-party functionality. We recommend following the steps outlined on our FAQ page to isolate the cause and identify the culprit. You can find the necessary steps here: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
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 for further assistance at WPML support forum.
Problem: If you're experiencing a blank page when trying to update a translation using the WPML translation editor, it might be due to insufficient WordPress memory limit. Solution: We recommend increasing the WordPress memory limit to at least 128MB. You can do this by adding the following code to your wp-config.php file:
Add it above the line /* That's all, stop editing! Happy blogging. */. After adjusting the memory limit, please verify it by navigating to WPML -> Support in your WordPress dashboard. If the issue persists, follow these steps: 1. Create a full backup of your site. 2. Update any outdated plugins or themes. 3. Flush any cache memory. 4. Activate WordPress debug mode by following this guide: Debug WordPress. 5. Deactivate all plugins, including WPML ones. 6. Activate a default WordPress theme, like Twenty Twenty. 7. Reactivate the WPML plugins. 8. If the issue disappears, reactivate your theme and other plugins one by one to identify the problematic one. 9. If the issue still persists, check for errors in the debug.log file in your wp-content folder.
If these steps do not resolve the issue, or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at WPML 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 for further assistance at WPML Support Forum.
Problem: The client's site is built with Elementor and the Woodmart theme. They have translated the attributes using WPML, but the filters are not showing in the translated language on the product category pages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WooCommerce → Settings → Products → Advanced. 2. Ensure that the option Enable table usage is disabled. This setting can prevent the attribute table from populating correctly in the secondary language. 3. Save the changes. 4. Clear the caches from your site and browser, then check if the filters appear in the translated language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check for any related issues. Also, verify that you have the latest versions of your themes and plugins installed. If you still need help, feel free to open a new support ticket on our support forum.
Problem: The client's website is set up in multiple languages, and they are using the Events Calendar with WPML for translations. The main issues were that events were only showing in the Spanish version and not in other languages like Catalan, and some strings from the Events Calendar were not appearing translated on the event pages despite being translated in WPML.
Solution: 1. To ensure events appear in all languages, we advised setting the translation preference for the 'tribe_events' post type to 'Translatable - use translation if available or fallback to default language' in WPML > Settings > Post Type Translation. 2. For the untranslated strings, we recommended rescanning the Events Calendar plugin for strings via WPML > Theme and Plugins Localization, then translating them in WPML > String Translation. If strings still did not appear translated, generating MO files through WPML > Support > Troubleshooting was suggested. 3. We also addressed a specific issue with the string 'Calendar' appearing twice by removing the duplicate translation in WPML > String Translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are unable to translate custom posts for blogs and boats on your website using WPML. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to the WPML >> Settings page. 2. Scroll down to the "Post Types Translation" section. 3. Set the blog and boats post types as "Translatable - only show translated items". 4. Clear all sorts of cache from your site/server/CDN and check if this resolves the issue. For more detailed instructions, please refer to our documentation here: Translating Custom Posts
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing a critical error after installing and activating the Sticky Links plugin while trying to edit a page. This occurs when WPML is installed but not fully configured. Solution: We recommend completing the WPML configuration before installing the Sticky Links plugin. This should serve as a workaround to prevent the critical error. 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 further assistance is needed, we encourage you to open a new support ticket at WPML support forum.
Problem: You are trying to assign a different domain for each language on your site using WPML, but the French domain redirects back to the English domain despite setting up different domains for each language. Solution: To resolve this issue, ensure that each domain is correctly configured to point to your WordPress site through the DNS settings. All your domains (or subdomains) should direct to the WordPress site where WPML is installed. This configuration is also can be handled by your hosting company.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: Der Kunde berichtet, dass seit der Installation von WPML alle Seiten im klassischen Editor geöffnet werden, anstatt im WPBakery Backend Editor. Der Parameter &classic-editor wird automatisch zur URL hinzugefügt. Solution: Wir haben festgestellt, dass dieses Verhalten nicht direkt durch WPML verursacht wird, sondern eine Funktion von WPBakery ist, die aktiviert wird, wenn Gutenberg deaktiviert ist. Der Parameter &classic-editor ist Teil des WPBakery Codes und wird hinzugefügt, wenn auf die Bearbeitung von Beiträgen zugegriffen wird. Dieses Verhalten lässt sich auch in einer Sandbox-Umgebung ohne WPML reproduzieren. Weitere Informationen und mögliche Lösungen finden Sie hier: https://wordpress.org/support/topic/how-to-remove-the-classic-editor-from-every-edit-url/.
Falls diese Lösung für Ihr Problem irrelevant erscheint oder veraltet ist, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
Problem: The client was updating WPML to version 4.6.15 and Elementor to version 3.26, following the recommended update procedure. After the update, the Elementor editor stopped loading.
Solution: We recommended enabling debugging on the client's site to identify any errors causing the issue. The debugging process involves: 1. Enabling the WPML debugging feature, as detailed in our documentation: https://wpml.org/documentation/support/debugging-wpml/ 2. Attempting to open the Elementor editor again to ensure that any errors are logged in the debug.log file located in the wp-content directory. 3. Sharing the errors from the debug log with us for further analysis.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
