Problem: The client is unable to trigger translations when updating a default language post. They expected a translation prompt but received no response. Solution: We recommended verifying that the code for the WPML Non-Persistent Cache plugin is correctly saved and placed. The correct code should be in a file named
wpml-non-persistent-cache.php
and added to the
mu-plugins
subfolder inside
wp-content
. This plugin helps prevent persistent caching issues that might be blocking the translation triggers.
If this solution does not resolve the issue or 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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an Error 500 when saving any existing posts in WordPress after updating the ACFML plugin. The error is caused by a TypeError in the HashCalculator.php file. Solution: We recommend updating the ACFML plugin to the latest version, which at the time of the support was version 2.1.2. To update, navigate to Plugins > Add New > Commercial tab and then check for updates.
Please note that this solution might be outdated or not applicable to your case. If after following these steps 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 the problem continues, please do not hesitate to open a new support ticket with us.
Problem: The client was unable to scan their customized roots.io Starter theme for new strings in the WPML settings. Despite trying to disable all plugins and switching to the default theme, the issue persisted. The client confirmed that the style.css was set up correctly and that the issue was not present in their local environment, suggesting a server configuration problem.
Solution:
We asked the client to provide temporary access to their WP-admin for further investigation and to confirm if their theme would work in a standard WordPress folder installation. We set up a sandbox site for the client to upload their theme to test if the issue persisted there. We also suggested setting up a staging site with a default WP folder structure to check if the issue was related to the custom configuration of the client's server.
It was confirmed that the issue wasn't happening on a WordPress default folder setup, but only in the custom folder configuration.
If you're experiencing a similar issue, we recommend checking your theme's style.css header, disabling any redirections, and testing your theme in a standard WordPress folder installation. If these steps do not resolve the issue, please consider setting up a staging site with a default WP folder structure to rule out server configuration issues on the client's server.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking 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 open a new support ticket.
Problem:
The client is having an issue with a redirect that has stopped working for a custom content type. The expected URL does not load and returns a 404 error.
Solution:
First, we confirm whether the code snippet provided above is still present in the current client theme. Then we suggest disabling all plugins except WPML to check if the issue still occurs.
If the issue persists, we provide an updated code snippet for the customer to try:
We advise the customer that we cannot offer support for custom code and that if the code stops working in the future, we will not be able to fix it. However, we have created a support ticket in our internal system to improve this behavior in future versions.
If the solution provided is not relevant because it is outdated or does not apply to your case, we recommend opening a new support ticket. We also strongly recommend reviewing the known issues, checking the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem:
since the latest update, all our ACF block / field labels need translating - we don't want this option and would like to keep field labels in the default language (English).
Solution:
I have checked this better and actually this is not a bug. It is a new feature, which allows the client to translate these labels more easily using the Advanced Translation Editor and its automatic translation feature.
