Problem: You have a custom 'options' page created with Advanced Custom Fields (ACF) and the options are not rendering in other languages when the language is changed. You've set the mode to 'Expert' and chose 'Don't translate' because the contents of the option page don't need to be translated (e.g., phone number). However, when you switch languages, the content is missing. Solution: Currently, the functionality to disable translation for ACF option pages and ensure they render correctly in all languages regardless of the translation settings is not available. This issue has been escalated internally as a feature request. As of now, there are no plans to implement this due to limited demand, but it remains open in our internal tracker for future consideration.
If this solution does not apply to your case, or if it becomes outdated, we recommend opening a new support ticket. We also 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. For further assistance, please contact us through the WPML support forum.
Problem: The client would like to lower the amount of HTTP requests, due to each language flag being loaded as an individual SVG file. This results in multiple HTTP requests, which increase Time To First Byte (TTFB) and initial rendering time, particularly affecting visitors on slower networks.
Solution: We have forwarded a feature request to load SVGs programatically instead of using SVG files, which is currently under revision. You can find a custom solution approach for the issue inside the comments of this ticket.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing outdated page previews in WordPress while using WPML, it might be due to WPML's parse_query flow setting a fixed single-post ID ('p') on the WP_Query. This issue occurs because during the preview, WordPress queries the latest autosave revision, but the 'p' set by WPML persists, preventing the latest revision from being fetched.
Solution: We recommend implementing a minimal, safe fix by modifying the WPML_Query_Parser::parse_query method. Here's a step-by-step guide: 1. Open the file located at
. 2. Locate the section where the post_type is computed. 3. Add a guard early in the method to clear any leftover single-ID constraints for revision queries. Here's the code you should add:
This change ensures that preview requests correctly fetch the most recent autosave revision without being pinned to an old revision ID. Normal WPML routing and translated front-end behavior remain unchanged.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where changes made to the Header elements for the Spanish and Polish versions of their site are being incorrectly applied to the Global Header instead of the respective language headers. This problem arose after manually editing headers created in the default language and attempting to translate them for other languages.
Solution: We recommend not manually editing Full Site Editing (FSE) templates for different languages as this approach is not compatible with WPML. Instead, you should: 1. Delete all problematic templates. 2. Create a new template in the default language using the Appearance > Editor option. 3. Translate the new template using the Translation Dashboard as outlined in our documentation here: Using Different Translation Editors for Different Pages. 4. If issues persist after following these steps, please open a new support ticket for further assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the problem persists, do not hesitate to open a new support ticket at WPML Support Forum.
Problem: Se stai cercando di tradurre i Valori di Attributes / Variations in un sito WooCommerce e non riesci a farlo tramite l'editor di WordPress, il problema risiede nel fatto che gli attributi per prodotto sono metadata e non tassonomie, il che impedisce la loro traduzione diretta. Solution: Per tradurre i Valori di Attributes / Variations, hai due opzioni: 1. Utilizzare l'editor di Traduzione Avanzato di WPML. 2. Creare attributi globali in 'Prodotti > Attributi' su WooCommerce, che, essendo tassonomie, possono essere tradotti tramite 'WPML > Traduzione delle tassonomie'.
Se questa soluzione non dovesse essere più attuale o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di verificare le questioni note, controllare la versione della correzione permanente e confermare di avere installato le ultime versioni dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
