Problem: You are experiencing issues with editing a page on your multisite setup, where attempting to edit the page forces a login screen, and subsequent login redirects you back to a different domain. Solution: We recommend checking the 'Automatically log in and log out users across all domains' option in your WPML settings. This setting can be found under WPML > Languages in your WordPress admin area. Enabling this option should resolve the issue of being redirected after logging in. If you need to log in again when trying to edit the page, this should be expected, but it should allow you to proceed with editing without further redirections.
Please note that this solution might be outdated or not applicable to your specific case. 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 issue persists, please open a new support ticket.
Problem: The client has enabled the Browser language redirect functionality with the setting "Redirect visitors based on browser language only if translations exist". However, they are experiencing issues as the site does not redirect to the Polish version when accessing the homepage with the browser language set to Polish. Solution: We explained that WPML performs the language redirect only once to allow visitors the option to switch languages manually. If WPML were to redirect to the browser's language every time, it would prevent users from choosing a different language after being redirected. We recommended checking the browser's cookies or using an incognito window to test the redirect again. Additionally, we provided a guide for further assistance: Automatic redirect based on browser language If the client needs to customize the behavior further, we suggested consulting our hooks reference: WPML Hooks Reference If the provided solution is not relevant due to being outdated or not applicable to the client's case, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client needed to set up user locale (language) via an API for a WordPress site using WPML. They wanted to update the user's language preference, which is collected in an external system, to be used by a membership plugin for sending localized messages. The 'locale' field in the wp_usermeta table was not being updated when the language was switched using the language switcher, only when changed in the admin panel.
Solution: We informed the client that the 'locale' field in the wp_usermeta table is not specific to WPML and is present even in a WordPress installation without WPML. This field is empty by default and only gets a value when the language is changed from 'Site default' to a specific language inside the user's WordPress profile.
If this solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. 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.
Problem: The client needs to know if they should register their test site with a new WPML license after cloning their production site. Solution: If you're experiencing issues after cloning your website and are unsure about the WPML license registration, we recommend that you unregister the license key from the cloned website and then register the new website with a new license key associated with that URL. Here are the steps to follow: 1. Unregister the license key from your website. For detailed instructions, visit Unregister WPML. 2. Register the new website / URL with a new key. For detailed instructions, visit Register WPML.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
