Problem: The client is experiencing an issue where a specific page on their website is redirecting to a 404 error page instead of displaying the intended content. Solution: We recommend clearing all caches related to the website, including any server-side caches and the browser cache. This action often resolves issues with outdated or corrupted cache data that might be causing incorrect page redirections.
If clearing the caches does not resolve the issue, it might be due to a configuration that is no longer applicable or a different underlying problem. In such cases, 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, please do not hesitate to open a new support ticket with us for further assistance. You can do so at WPML Support Forum.
Problem: The client has an ACF field in the option page of their site under development, which is not autotranslatable. Solution: We explained that ACF Option pages cannot be translated with the Advanced Translation Editor, which is why automatic translation is not possible. We recommended following the guide to translate ACF Option Pages. For detailed steps, please visit: Translating the ACF Options Page Custom Fields with WPML.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
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.
