Not WPML issue

Problem:
The client's website was experiencing slow performance due to a high number of database queries generated by WPML when handling ACF nested repeater fields in posts. The client wanted to minimize these queries by ensuring WPML does not translate these fields.

Solution:
We recommended setting the custom post types (CPTs) like 'Songs' and 'Guided Lessons' to non-translatable in WPML settings to prevent WPML from processing these fields. Additionally, to address the high number of queries caused by the Search & Filter plugin and taxonomy labels registered by CPT UI, we suggested:
1. Adding the following code to the theme's functions.php file to bypass WPML’s term ID adjustment:

add_filter( 'wpml_disable_term_adjust_id', function() { return true; } );

2. Replacing CPT UI’s dynamic taxonomy registration with static code by copying the code from CPT UI → Tools → Get Code and adding it to a custom plugin.

These changes aimed to reduce the load caused by unnecessary translations and database queries. We advised testing these changes on a staging site first and ensuring a full backup before applying them to production.

If this solution does not apply to your case, or if it seems 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 visit our support forum at WPML Support Forum.

Problem:
The client is experiencing an issue where the Complianz cookie banner displays only Slovak text across all language domains despite having translations available in WPML String Translation. This issue persists even after multiple troubleshooting steps, including rescanning plugin strings, purging caches, and testing in different configurations.

Solution:
We recommend checking the compatibility of Complianz with the WPML 'different domain per language' setup. It's important to ensure that all strings are correctly translated and rescanned in WPML. If the problem continues, try the following steps:
1. Change the URL format to 'Different languages in directories' temporarily to check if the issue is related to domain configuration.
2. If the issue persists, it might be a deeper compatibility issue or a problem with how Complianz handles default language content. In this case, further investigation into the plugin's interaction with WPML is necessary.
3. Consider testing on a minimal setup or a clean installation to isolate the issue.
4. Review the related known issues on WPML Errata and follow any relevant solutions.

If these steps do not resolve the issue, or if the solution provided here becomes outdated, we highly recommend opening a new support ticket. Also, check the related known issues on WPML Known Issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please contact our support team at WPML Support Forum.

Problem:
The client was unable to translate media files using WPML as the page displayed a 'setup required' message without any actionable buttons to proceed.
Solution:
The issue resolved itself when the client attempted the process again the following day and successfully clicked on 'finish setup'. If you're experiencing a similar issue, we recommend trying to access the setup again. If the problem persists, ensure that your WPML and other plugins are up to date. It's also advisable to check for any known issues related to media translation at WPML Known Issues.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.