Problem: The client reported an issue where a dynamic ACF image that displays correctly on other posts was not showing on a specific translated post. The expected behavior was for the image URL to appear in the Advanced Translation Editor, but it was missing, leading to the image not being displayed on the front-end. This issue was occurring despite the functionality working correctly on other parts of the website. The client was using the Avada theme.
Solution: We recommended the following steps to resolve the issue: 1. Delete the image in the default language post. 2. Update the post. 3. Re-upload the image and update the post again. 4. Update the translation. 5. Check if the image appears on the front-end.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we encourage you to open a new support ticket. We also highly recommend checking the related 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.
Problem: The client reported that a character 'P' from 'Antwerp' was missing in the English translation of the concert layout, although it was present in other areas. Solution: We found that the issue was caused by an additional space created using HTML (
) to separate the terms. We recommended removing this space, which resolved the issue, and the missing character 'P' started to appear correctly in the English version of the concert. If the client needs to separate terms, we suggested using a comma (,) instead of the HTML space. If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: The client reported an issue with WPML and ACF relationship on the 'news' post type, where sections based on ACF relationships were missing in translations. Solution: 1. We asked the client to elaborate on the issue and to provide screenshots or a screen-recorded video. 2. We requested the client's Debug information to better understand the site configuration. This information can be found in our documentation: http://wpml.org/faq/provide-debug-information-faster-support. 3. Upon further investigation, it was determined that the issue was related to a CSS class causing the sections to not display correctly. We provided a CSS snippet to resolve the issue:
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.
Problem: The client reported that press articles, which are based on an Advanced Custom Fields (ACF) relationship, were missing from artist pages on their website. Solution: We resolved the issue with the missing press articles on the artist pages. If you're experiencing this, we recommend you try the resaving method we provided in a previous support ticket. This method should restore the missing content.
Problem: The client is experiencing an issue where text links created with the Avada theme link to the original language instead of the translation, despite the pages being translated with the WPML Advanced Translation Editor (ATE). This issue does not affect button links.
Solution: We recommend checking the translation of the home page in ATE and searching for the URL to translate it manually. For automatic translation of internal URLs in Avada element titles, we suggest adding the following custom XML configuration code:
After adding the code to WPML > Settings > Custom XML Configuration tab, edit the homepage in the Dutch language and click on Update to refresh the translation. For further guidance, refer to the following documentation:
Problem: The client is experiencing an issue where Advanced Custom Fields (ACF) are registered to the incorrect language (English), despite being created in Dutch. Solution: If you're experiencing issues with ACF fields being registered to the incorrect language, and you're unable to change the source language for certain strings because the option is greyed out, it's likely due to those strings being part of a String package. To resolve this, you need to select all the strings within that particular package to modify their source language. We recommend following the steps in this video to change the language of all strings under the ACF domain to the default language: https://tinyurl.com/ym9js9gq. If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us: Contact WPML Support.
Problem: The client is experiencing an issue with duplicate Avada post cards appearing on their website. Solution: 1. We asked the client to provide the URL of the page where the duplicated post cards are visible. 2. Upon reviewing the provided URL, we advised the client to only create the post cards in the default language (NL) and then translate them to English (EN), instead of creating them in both languages. 3. We also instructed the client to manually re-establish the connections for the translations by following the steps outlined in our documentation. The client should identify each untranslated "Post Cards" and reattach them to the appropriate language, making sure to set the correct default language if necessary. Here is the documentation link for reference: https://wpml.org/faq/how-to-link-already-translated-pages/.
If this solution doesn't look relevant to your issue, please feel free to open a new support ticket with us here.
