Available Solutions

Problem:
The client reported that their website was going down every hour due to increased server memory consumption when WPML was enabled. Without WPML, the server memory usage was at 1GB, but with WPML activated, it increased to 3GB, causing MySQL crashes.
Solution:
We reviewed the site's settings and found that the PHP memory limit was set to 256MB, but the WordPress memory limit was only set to 40MB. We increased the WordPress memory limit to 250MB and enabled the WPML SEO feature. After monitoring the site for several hours, we did not observe any resource exhaustion or significant slowness. We asked the client to test the site and inform us if the issue persists or if there are specific steps that could reproduce the problem.

If you're experiencing similar issues, we recommend checking your WordPress memory limit and adjusting it accordingly. It's also beneficial to enable WPML SEO and monitor your site's performance. If the problem continues, or if this solution seems outdated or not applicable to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket in our support forum for further assistance.

Problem:
The client needed assistance with translating the site title/tag.
Solution:
We informed the client that they had already successfully translated the site title using WPML's String Translation feature. We provided a link to the specific section in the WPML String Translation page where the translation was made. Additionally, we shared two screenshots to show where the translation was applied and confirmed that it was displaying correctly on the front-end of the website.

If you're experiencing issues with translating your site title or tag, we recommend checking the WPML String Translation section to ensure that the translation has been applied. If you find that the translation is not displaying as expected on the front-end, please verify that you have followed the correct steps in WPML's String Translation.

Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we 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. If you still need assistance, please do not hesitate to open a new support ticket in the WPML support forum.

Problem:
The client needed to display different logos for different languages/domains on a multilingual site using WPML and the Buddyboss theme. They managed to translate the logo using its ID, but the translated logo was overriding the default logo in the Buddyboss theme settings.

Solution:
We asked the client to provide the media IDs for both the default language logo and the translated logo. We also requested temporary access to the client's site to investigate the issue further. We assured the client that we follow strict privacy and security policies when handling their information, as detailed at our privacy and security policy.

We reminded the client to back up their site before providing access and informed them that we would handle one issue per ticket to maintain focus and efficiency. We asked the client to open a new ticket for each unique issue they were experiencing.

If the solution provided here does not apply to your case, or if it seems outdated, we recommend checking the 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 you still need assistance, please do not hesitate to open a new support ticket in our forum at WPML support forum.

Problem:
The client was trying to translate a Theme Builder layout using Divi Builder. When they loaded the content in a second language, it appeared the same as the default language. Editing the content in the second language also affected the default language. Additionally, the shop page appeared translated, but a 404 error occurred when trying to visit the page in the second language.

Solution:
1. We recommended following the guide to translate Divi Builder layouts and theme builder templates, which can be found here: https://wpml.org/documentation/theme-compatibility/divi-builder/#translating-divi-global-items.
2. We requested the URL and the name of the shop page in the default language, as well as the URL that returned a 404 error.
3. We asked for temporary access (wp-admin and FTP) to the site to investigate the issue further, ensuring that the client followed our privacy and security policy: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/.
4. After receiving access and investigating, we found that the issue might have been related to caching. We confirmed that the URLs for both the default language and the second language were working correctly.

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 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. If you need further assistance, please contact us in the WPML support forum.