Home›Support›English Support›[Resolved] Split: Other languages look like they're running on an older version of the page
[Resolved] Split: Other languages look like they're running on an older version of the page
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with the header and footer not updating across all languages after making edits. The edits are made directly via Editor → Patterns → Header, which causes synchronization issues with WPML. Solution: We recommend the following steps to ensure proper synchronization of translations across all languages: 1. Create and edit the header pattern in the default language only, using the top bar language selection. 2. Ensure everything looks correct in the default language. 3. Navigate to WPML → Translation Management 4. Send the header/pattern for translation. 5. Translate it using the WPML editor. This process helps WPML to properly track and synchronize the translations across all languages. Additionally, when updates are made to texts, patterns, etc., you only need to re-translate the specific items that were changed in the default language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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.
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.
Thanks alot. This indeed fixed the issue of the ACF posts. Appearently we just falled ACF in the Dashboard page instead of FAQ or Opdrachten to be translated. I think that caused the issue.
We were able to fix the Option page to by translating in manually.
The first 2 questions are completely fixed now.
Now we just need to see if we can fix issue 3 and 4. The running on old version (Seems like it only effects Patterns like Header/Footer) and the Forminator field.
We saw forminator wasn't supported but are wondering if in some way we will still be able to translate it.
We're also running some custom plugins on the website. Would we be able to translate those too? We don't mind trying to implement WPML support in it if needed.
In this ticket, let’s focus on the header and footer first.
I’ve checked the EN homepage and I don’t see any differences in the header compared to the default language.
- hidden link
As for the footer, it seems to be displaying correctly, but it is missing some data coming from the ACF Options page. You will need to add that content for the secondary language as well.
Please let me know how can I see this issue and I will check it out,
It's mainly if we make edits to the header and footer. It updates in the language the site is set on at that moment, but not the others. We just edit from Editor -> Patterns -> Header.
I've attached 3 screenshots. The difference is the language selector in the top-right of the header;
1. Current view in editor
2. View on swedish page
3. View on any other page (main language, english, italian etc..)
Thank you for getting back to me and for the screenshots.
I can see the issue with the language switcher on the live site. However, since I’m currently checking the staging/dev setup, I’m not able to reproduce or verify it there, so I can’t investigate further at the moment. Could you please share an example from the dev site as well?
That said, based on your description, it looks like you are editing the header directly via Editor → Patterns → Header. This approach can lead to this kind of issue with WPML, as patterns edited this way are not properly synchronized across languages.
The recommended workflow is:
- Create and edit the header pattern in the default language only (top bar language selection)
- Make sure everything looks correct there
- Then go to WPML → Translation Management
- Send the header/pattern for translation
- Translate it using the WPML editor
This way, WPML can properly track and synchronize the translations across all languages.
So after every update we make to the website (texts, patterns etc) we have to update everything with Translation Management for it to update across all languages?
Not everything needs to be updated every time only the parts where you’ve made changes in the default language.
So the correct workflow is:
- Make your changes in the default language
- Save/update the content (page, pattern, template, etc.)
- Then re-translate only that specific item via WPML (Translation Management or the editor or via automatic translation)
