Problem: If you're experiencing issues where a QueryLoop does not display subpages in Spanish on your translated page, despite having the 'Set page parent for translation according to page parent of the original language' setting enabled, you are not alone. Solution: We recommend starting by closely examining the QueryLoop’s language/context resolution within the Site Pattern—especially how it detects and queries translated children in non-default languages. You should also investigate any WPML compatibility issues with full-site editing patterns and QueryLoop blocks. It's crucial to ensure that all page and pattern-level translation links and caches are validated. Avoid reiterating basic sync/edit/cache-clear steps; instead, review block output, site pattern translation integrity, and theme/block compatibility in the Spanish context. If necessary, collect a copy of relevant pattern and post data. 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 was experiencing issues with menu item links and labels not updating correctly in the Spanish version of their site. Specifically, the link for 'Recetas' was incorrect, and the footer label 'Guarniciones' was not updating to 'Extras' despite being translated. Solution: The client resolved the issue by editing the menu items to different values, then translating them, and finally restoring the original English values and retranslating. This process seemed to trigger a cache refresh which resolved the issue. Additionally, the WPML support team had suggested verifying and updating translations via WPML → String Translation, synchronizing menus through WPML → WP Menus Sync, clearing site and browser cache, and checking server requirements including increasing the WP_MEMORY_LIMIT.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 visit our support forum at WPML support forum.
