Problem: The client reported slow load times when the WPML String Translations plugin is enabled. They noticed that disabling the plugin significantly speeds up the page loads. They also mentioned using the Index WP MySQL For Speed plugin, which only slightly improved the situation. The client was concerned about the storage of translation files and the potential impact of custom actions on performance. Solution: We recommended the following steps to troubleshoot and potentially resolve the issue: 1. Use the Query Monitor plugin to compare performance with and without WPML plugins enabled to help identify slow queries. 2. Ensure all WPML plugins are updated to the latest versions. 3. Test in a minimal setup by switching to a default theme, such as Twenty Twenty-Four, and disabling all plugins except WPML and ACF. Then, gradually re-enable the theme and other plugins to check if a specific component is causing the issue. 4. If the issue persists with only WPML and the default setup, it might be a WPML-specific issue, which we will investigate further. 5. Check with the hosting provider to review server load, cache, or configuration differences, as the local environment was much faster than production. 6. If applicable, provide a staging site or a duplicator package for further investigation. 7. Since the issue related to a read-only languages directory mentioned in the Pantheon errata does not apply (as translations are being generated and stored), there is no need to apply the workaround in wp-config.php. 8. Removing the
after_setup_theme
action could help improve performance if it was doing additional processing on every request.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client wanted to know how to use a single PO file to apply translations across multiple sites without manually importing it into each site. Solution: We recommend manually importing the same PO file into each of the client's sites. Currently, there is no automatic way to synchronize or share PO files across multiple sites. Each site must have the file imported individually to ensure the translations are applied correctly.
Please note that this solution might be 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where the 'This site is registered on WPML.org as a development site' notice still appears after following the setup instructions, and you cannot add a new plugin via the admin UI, this might be due to WPML detecting a change in the site URL. Solution: We recommend following the steps provided in the migration banner that appears when WPML detects a site URL change. It's important to ensure that if both sites involved share the same site key and one of them was moved or duplicated, and both sites are currently active, each site must have its own unique site key.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if you need further assistance. You can do so at WPML support forum.
