This thread is resolved. Here is a description of the problem and solution.
Problem: The client was experiencing issues with WPML not replicating designs correctly across translations, affecting page layouts, post types, and typography settings. Specifically, there were problems with 'concert' postcards not displaying correctly due to conditional logic based on term IDs, and global typography settings not being carried over in translations.
Solution: 1. We recommended comparing the original and translated versions of the 'concert' postcards to identify any discrepancies in settings or options. 2. We advised correcting the category ID for the English language postcard, as WPML does not automatically register the translated term ID used in Avada's conditional logic. 3. We confirmed that switching to the 'WordPress Editor' would require sticking with it, as switching back to the WPML Editor would necessitate re-translating the entire page. 4. For the Avada options, we provided a link to the documentation on using WPML with the Avada theme: https://wpml.org/documentation/theme-compatibility/using-wpml-with-the-avada-theme/#setting-theme-options 5. To address a critical error on a specific page, we suggested performing a backup, permanently deleting the English language page, and re-translating it from Dutch.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us: 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.
Wow I hadn't noticed that. Good catch! I cannot think of why that would happen. This is, I think, the last major issue. I was able to fix almost everything else. A few loose ends here and there that I will clean up tomorrow. I hope I can push this version live soon.
Hi Kor. I cleaned up a few design things this morning. I noticed still a few things going wrong. I will list them, just to be sure you've got everything you need.
On concert pages all post cards based on ACF relationships seem to go wrong in translations
Example: hidden link
Avada layout for concert pages: hidden link
ACFs for concerts: hidden link
Screenshot with explanation which post card relates to which ACF field: hidden link
On the news archive page, the 'In the press' post cards at the top of the page are in the wrong order in the translations. I translated this page with the Advanced WPML editor, so it is strange the order isn't carried over to the translation.
Page: hidden link
Page admin: hidden link
New threads created by Kor and linked to this one are listed below:
It's the same issue here. When I change the post into drafts, it shows correctly. I will have to escalate this to our 2nd Tier Support for further assistance.
For that concert it seems correct, but for none of the others the artist post card is shown correctly. Why is that happening?
Some examples: hidden link hidden link
Amazing, thank you! I resaved everything and those two postcards (artist profile photo at the top + the info box beneath the programme) seems to work. There are still a few issues on concert pages, though. It will be a similar issue as it also relates to a post card - ACF relationship.
Below the artist info box there is information about the concert venue. It works perfectly in the original language, but not in the translation
Let's use a different concert post, because it will illustrate the issue more clearly. The venue section consists of two post cards that pull data from the post type "Locaties" ( hidden link ) based on an ACF relationship set on the concert page admin.
WPML isn't registering the relationship though. Every concert post is only showing data from the first location in the admin list (Phillharmonic Hall in Liege) instead using the data from the related location. Compare the venue section on this concert post:
hidden link hidden link
The location should be Amare in The Hague. Also, one of the post cards is displaying pagination, which tells me it's pulling multiple locations - instead of using it's 1 related location.
Fixed! Thanks Kor! I'll close this ticket. I've asked my colleague to do a final check. If OK I will push live some time later today. I'll update you via the other ticket.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
