Problem: The client is experiencing an issue where the Dutch archive for their 'destinations' taxonomy incorrectly loads posts from other terms after the initial correct batch. This problem occurs during AJAX pagination and affects archives like /nl/bestemmingen/azie/japan/. Solution: We identified that the theme's AJAX filter might not be compatible with WPML. Our 2nd Tier Support suggests either keeping the 'destination' taxonomy untranslated or deactivating the AJAX pagination plugin as potential solutions. Unfortunately, due to the theme's limited use and lack of compatibility with WPML, further investigation by our support team will not proceed. If deactivating AJAX pagination is a temporary workaround, we recommend contacting the theme developers for a permanent fix, providing them with details of the issue.
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: The client is experiencing 404 errors when accessing translated custom taxonomy pages. Solution: If you're encountering similar issues with 404 errors on translated taxonomy pages, we recommend the following steps: 1. Navigate to WPML > String Translation. 2. Search for 'destinations' and ensure the 'Exact match' checkbox is checked. 3. Delete all translations of the string 'destinations' that are not capitalized. 4. Go to WPML > Settings > Taxonomy Translation and re-translate the slug for the taxonomy. Additionally, check if your theme is listed on our compatibility list at https://wpml.org/theme/. If it's not listed, it might be worth reaching out to the theme's author to confirm compatibility with WPML.
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 at WPML support forum for further assistance.
Problem: The client is experiencing issues where manually translated posts from English to Dutch using WPML revert back to English in certain parts such as paragraphs, buttons, and affiliate links. This occurs even after translations have been set and not modified for a period. Solution: 1. Ensure that you are using a consistent method of translation. Mixing translation methods (ATE/WPML editor and manual/WordPress editor) can lead to content being overwritten when the default language page is updated. Choose one method and stick to it. For more details on using different translation editors, visit Using Different Translation Editors for Different Pages. 2. Update the WPML plugin and all related add-ons to the latest version to ensure all bug fixes and improvements are applied. Instructions for updating can be found at How to Install WPML. 3. If issues persist after updating and ensuring consistent translation methods, consider setting up a staging site to replicate the issue, which can help in further troubleshooting.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, we recommend opening a new support ticket. We also 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. For further assistance, please contact our support at WPML Support Forum.
Problem: The client was experiencing 404 errors on their multilingual website when accessing translated pages and taxonomies for the first time. The issue persisted even after disabling various caching solutions and plugins. The WPML String Translation plugin was identified as part of the problem, particularly when switching between languages on posts. Solution: We recommended the following steps to address the issue: 1. Navigate to WPML > String Translation. 2. Search for
wc/file/transient
and
wc-api
under the WP Endpoints domain. 3. If these strings are translated (indicated by a pencil icon below the language flag), select both and delete them from String Translation. 4. Go to "Settings > Permalinks" and resave the permalink structure. 5. Clear the caches from the site and browser, then check the page again. Additionally, we suggested checking the guide on handling .htaccess issues with WPML at https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
If this solution does not resolve the 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 problems persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing an issue where after editing the formatting of a translated post, the translation disappears and cannot be added back. The translation saves in the advanced editor, but does not appear in the dashboard. Solution: We recommend the following steps: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Enable the option "Use the previous version of the Advanced Translation Editor." 4. Refresh the page. Next, follow these steps: 1. Navigate to your Dashboard > Pages. 2. Open the edit screen of the original page. Look for a pencil/circle/gear icon in the sidebar options under the "Languages" section. 3. Make a small change, such as adding an extra blank space at the end of a sentence or paragraph. 4. Save it. You should now see a circular arrow beside the second language's links, indicating that an update is required. 5. Edit the translation again and ensure it is saved up to 100% translated. If this solution does not resolve your issue or seems irrelevant due to being 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.
