Problem: You are trying to translate the button of the loop item in the loop grid on your WordPress site using WPML, but when you translate the Italian version, it also changes the German version. Solution: To resolve this issue, here are the steps you should follow: 1. Navigate to Templates -> Saved Templates. 2. Click on All, and then go to the loop tab to access the specific template you need to translate.
After translating the template, please check if the issue with the language versions affecting each other is resolved.
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 the problem persists, please do not hesitate to open a new support ticket. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing 404 errors when switching between translated slugs for a custom post type in different languages using WPML. The issue arose after setting different slugs by language in the theme settings, which conflicted with WPML. Solution: We recommended removing the language-specific slug entries in the theme settings that were conflicting with WPML. This adjustment should resolve the 404 errors when switching languages. If you're experiencing similar issues, we suggest checking your theme settings for any language-specific configurations that might interfere with WPML's slug translations.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page and verify that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket for personalized assistance. You can do so here: WPML support forum.
Problem: The client reported that after moving from a beta page to a live environment, some parts that were previously translated via string translation were not showing as translated on the front end. Solution: We recommended the client to first perform a full backup of their site. After that, we instructed them to access their server via FTP and navigate to the
wp-content/languages
folder. We then advised them to remove all language files, leaving only the three folders as shown in our provided screenshot. This action should resolve the issue.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
