Problem: The client needed to ensure that their location pages were not published in Spanish and that visitors would only see the English version, even if they manually added
/es/
to the URL. Solution: We checked the location posts and confirmed that the language switcher does not appear, indicating that the posts are available only in English. If the client wants to prevent access to the Spanish version even when
/es/
is manually added to the URL, we advised setting the post type to
"Translatable - only show translated items"
and not translating the posts. This will ensure that any attempt to access a Spanish URL will redirect to the English version automatically.
Problem: The client is experiencing an issue with automatic string translation in WPML, receiving an error message indicating a problem connecting to automatic translation. Despite confirming that the REST API is enabled and deactivating all other plugins, the issue persists. Solution: We recommend checking if the
eval()
function is enabled on your server, as WPML's TWIG framework requires it for template compilation. This function is essential for the operation of many templating engines, including TWIG, which WPML uses. It allows for faster execution through OPcode caching and ensures safe usage with WPML due to extensive checks and sanitation. If
eval()
is disabled, it might be due to extensions like Suhosin, which can be configured by your hosting provider. For more details, please refer to our documentation on minimum requirements: https://wpml.org/home/minimum-requirements/#eval-usage.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 the problem persists, please open a new support ticket for further assistance at WPML support forum.
