Taxonomy slug not updated with change of url domain

This thread is resolved. Here is a description of the problem and solution.

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/.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Not WPML issue

This topic contains 2 replies, has 2 voices.

Last updated by misoM 9 months ago.

Assisted by: Prosenjit Barman.

Author	Posts
April 18, 2024 at 11:33 am #15538033
misoM	Tell us what you are trying to do? I changed the domain of secondary language where categories were already created. But the category slugs and archive pages are still pointing to the old domain in which they were created. New categories created have correct slugs. Old categories have incorrect slug base. Example> hidden link Step1 visit this page Step2 Hover over the name "Koza" in the breadcrumb Step3 You will see old domain name and old slug name> hidden link It should show reviell.si/category/koza I tested with creating a new category and it points like it should to reviell.si and with correct slug name
April 19, 2024 at 7:01 am #15541971
Prosenjit Barman Supporter Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00)	Hello There, Thanks for contacting WPML Support. I understand the issue you're having and will try my best to assist you in this matter. The link targets might not have been updated properly yet, which is why, they still pointing to the previous subdomain. Please try the following and check if that helps in solving the issue. - Please go to "WPML > Settings" and scroll down to the "Translate Link Targets" section. - Click on the "Scan now" button and wait till the process is finished. - Once done, please clear the object caches from the backend. - 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 - Once done, clear the site caches and check if you're still having the issue in the frontend. Please let me know how it goes. I will be happy to help if you need further assistance in this matter. Best regards, Prosenjit
April 21, 2024 at 4:10 am #15546614
misoM	Sorry if I'm replying twice but I did one reply and I don't see it now. I did "Scan now" but it change 0 links and I also clear the cache inside settings. I don't exactly understand how to do those> -- Assign translation status to duplicated content -- Set language information -- Fix post type assignment for translations .. but I don't think it is relevant since> - categories link to the old domain name - slugs did not change, when they are changed with taxonomy category translations Thank you, Best,
April 21, 2024 at 5:06 am #15546636
misoM	Hello. The inner cache was the problem and is now resolved. Thanks