[Resolved] UAGB container link translation not working
This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to change the links inside a UAGB container to the correct Spanish links using the WPML editor, but the changes do not persist on the frontend. The links revert to the English version after some time.
Solution: We recommend adding the following XML configuration to ensure the links inside the UAGB container remain in Spanish:
Add this XML in WPML -> Settings -> Custom XML Configuration. After adding, follow these steps: 1. Open the English version of the page. 2. Make a minor edit to trigger a translation update. 3. Update the Spanish translation and ensure the links are translated correctly in ATE.
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, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, please open a new support ticket.
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.
Background of the issue:
I am trying to change the links inside a UAGB container for the proper link in Spanish from the WPML editor, but it doesn't change on the frontend. I also changed it manually from the site page editor, and it works temporarily, but after some hours, the links change back to the English version. URL: hidden link
Symptoms:
The category links on the slider carousel container do not reflect the changes and revert to the English version after some time.
Questions:
Why do the links inside the UAGB container revert to the English version after some time?
How can I ensure the links remain in Spanish on the frontend?
I'm wondering that your provided access information has been removed from the ticket.
I need to take a closer look at your site. So I request temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.
Your next answer will be private, to share this information safely.
Also provide detailed steps to reproduce the issue and links to pages in the admin and on the frontend.
IMPORTANT: Please take a complete backup of the site to avoid data loss. I may need to activate/deactivate plugins also.
I just wanted to update you that our team is looking into the matter, however, in the meanwhile you can fix this by going to WPML > Settings > Translate Link Targets.
I've added this in WPML -> Settings -> Custom XML Configuration in your test site. After that I did the following:
- Opened the English (default version) of hidden link.
- Added some dots to the title and saved, to trigger translation update.
- Updated the Spanish translation and in ATE, translated the links accordingly.
After completing the translation, it is working fine on the frontend now.
Hi, I tried to reply on prod. Finally, I could fix it, but I don't know if it will be temporary:
First of all, ATE doesn't allow me to translate regarding a markers problems error (see screenshots). I switched to the classic editor, and after some attempts and cleaning the cache, finally it worked.
Then I tried to delete the dots and all the link changes were missing again.(see screenshots)
I attempted a couple more times, after clean cdn and all server caches, and left for some minutes. Now it looks okay. Will see if it last or not. I'll keep you informed.
That XML fix isn't temporary, you can keep it in WPML -> Settings -> Custom XML configurations and it doesn't affected by any update (i.e. plugin or theme).
On the other hand, our team has also published these changes in theme's configuration files, which are automatically downloaded and propagated. So in case if you loose that XML, it still works fine.
For the other issue related to markers, I recommend opening a separate ticket/chat because as per forum policy we can only handle one issue per ticket/chat. So you can get more to the point help, without mixing up several issues in one long ticket.