Problem: The client is managing a multilingual site with categories translated into multiple languages. However, links for one specific category in two languages are incorrectly pointing to the main domain (.com) instead of the language-specific domains, causing 404 errors. Solution: First, from the default domain, navigate to WPML > Taxonomy Translation and select the Category from the dropdown menu. Edit the Czech translation of that particular category and ensure all updates are applied. After this, clear the object and site caches, and check if the issue persists. If the problem continues, follow these steps: - Go to WPML > Support > Troubleshooting - Click the following buttons: -- Clear the cache in WPML -- Remove ghost entries from the translation tables -- Assign translation status to duplicated content -- Set language information -- Fix post type assignment for translations -- Update domain name in language switcher settings - Clear the Object caches and verify the changes.
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 still exists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client changed the domain of the secondary language and noticed that the category slugs and archive pages were still pointing to the old domain. This issue was only affecting old categories, not the new ones.
Solution: 1. Navigate to WPML > Settings and locate the Translate Link Targets section. 2. Click on the Scan now button and wait for the process to complete. 3. Clear the object caches from the backend. 4. Go to WPML > Support > Troubleshooting and click on the following buttons: - Clear the cache in WPML - Assign translation status to duplicated content - Set language information - Fix post type assignment for translations 5. After completing these steps, clear the site caches and verify if the issue is resolved on the frontend.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
