Problem: The client is setting up different domains per language for their WordPress site using WPML. The primary domain is set for English, and a subdomain is intended for Chinese. However, the client encounters an error message stating 'The domain you have entered is invalid' when trying to use the subdomain for Chinese. Additionally, there is confusion about whether using 'http://' instead of 'https://' could pose a security risk. Solution: We advised the client that the HTTP setting is automatically set on the left, and it should not be added twice. It's fine to enter the subdomain as 'zhcn.starrealties.com' without 'https://' in the site settings, as it might still redirect correctly on the front-end. We also suggested checking if the subdomain redirects properly by translating a page for testing purposes and then attempting to access the translation to see if the subdomain is being used for the secondary language. If issues persist, we recommended providing temporary access (wp-admin and FTP) to the site for further investigation, ensuring that all site details are kept private and secure, as outlined in our Privacy and Security Policy.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if further assistance is needed.
Problem: The client needed to share their WordPress admin information safely with the WPML support team but was unsure how to do so securely. Solution: We advised the client to use the private field provided for access details when communicating through the WPML support forum. If the private field is not visible, the client should request the supporter in the ticket to enable it, ensuring that credentials are not publicly exposed. For further guidance, we recommend checking the screenshot at https://prnt.sc/eIM4Z-iuYZaF.
If this solution does not apply to your situation, or if it seems outdated, please do not hesitate to open a new support ticket. We also highly recommend visiting https://wpml.org/known-issues/ to check for related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
Problem: The client installed WPML on a WordPress site that already had Polylang installed, leading to a fatal error due to a function name conflict. Solution: We recommend deactivating the Polylang plugin if you wish to use WPML, as both plugins cannot operate simultaneously due to overlapping function names. This step should resolve the fatal error encountered during the WPML activation.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. Should you need further assistance, we highly recommend opening a new support ticket or visiting the WPML support forum.
