Home›Support›English Support›[Resolved] Blog category ACF field localized links keep reverting to English links for French categories
[Resolved] Blog category ACF field localized links keep reverting to English links for French categories
This thread is resolved. Here is a description of the problem and solution.
Problem: The client was experiencing an issue where links in the content of an ACF field for French categories were reverting to English during the localization process, despite other content remaining in French. The ACF fields in both the blog post and the category had the same name, causing a mix-up during translation. Solution: We recommended renaming the ACF field in the category to a unique name to avoid conflicts during the translation process. The client implemented this change by renaming the category field to 'cat_next_steps_cta', which resolved the issue. We also advised using unique field names globally in the future to prevent similar problems.
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 issues persist, please open a new support ticket at WPML support forum.
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 localize links in the content of an ACF field for French categories. The localization team noticed that these links keep reverting to English links. We update the field to change the links to French, but during the localization process, they revert back to English. All other content remains in French. We have updated all the WPML plugins to the latest version. Here's a quick video: hidden link
Symptoms:
Links in the ACF field content revert to English links instead of staying in French, while all other content remains in French.
Questions:
Could you please help us track down what's causing the links to revert to English?
In your reply and video, you mentioned that this happens during the localization process. Can you please share more info or a video about when and how this happens? It is not very clear what exactly are the steps that cause links to revert back?
Here is what the localization team shared:
1. They import the localized content into WPML
2. They check format/display and links. At this point all the links in the Next Steps category are in French.
3. They open the article in WPML to handle SEO.
4. They publish the article.
5. At this point they see the links have reverted to English (which was not the case in step 2)
thanks for getting back, but I would still need more info.
Maybe the best would be to record a video of the all steps showing and explaining what and how it goes wrong? I am not sure how you are importing, also how does updating an article in the WPML editor affect category links?
It could also be related, depending on your steps, that you are importing content but then readjusting content via WPML editor, which is expected to go wrong, imported content can not to be edited via WPML ATE editor, you would need to re-do it in WPML editor or switch to WP editor and do the translation manually. Also, I am not sure how you are translating / adjusting via WPML, there are different ways.
Hi Drazen, I think we may have figured out the problem. The blog post and the category both have an ACF field with the same name: next_steps_cta. We believe that during the translation process, this field is getting criss-crossed between the post and the category. The blog post next_steps_cta is typically blank so it's pulling in the English and then when it comes back it's shoving the localized content (but with English links) into the category next_steps_cta field instead of the blog post next_steps_cta field. We are going to try renaming the category field to cat_next_steps_cta to prevent a criss-cross and see if that resolves the problem.
That indeed was the problem. Changing the name of the ACF field on the category resolved the issue. However, I want to point out that this is a new problem and wasn't happening in the past so something changed that caused this. In my opinion, we should be able to have an ACF field with the same name on the category and on the blog post, but in the future I will definitely use unique field names globally to prevent any issues with WPML. Thank you! Happy Friday!
