Problem: The client is experiencing issues with links on a Spanish site still pointing to UK pages despite using the WPML Link Translation tool. The problem affects about 500 links, particularly absolute URLs in buttons, which do not automatically translate in the Advanced Translation Editor (ATE). Solution: We identified that the links need manual translation and recommended clearing the site's cache to ensure the correct links display. Additionally, the client should adjust the Advanced Custom Fields (ACF) Link Fields setting from "Translate" to "Copy" to allow automatic adjustment of links. It is also advisable to set all ACF Field Groups containing fields translated with the WPML Translation Editor to "Same fields across languages" for consistency. For more details, visit WPML documentation on translating sites built with ACF.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are considering a multisite setup where the main site (example.com) does not use WPML, and a subsite (example.com/en-us/) uses WPML. You are concerned about potential conflicts between the local and international sites on the same root domain. Solution: We can confirm that in a Multisite network, each site operates with its own independent language setup. Therefore, WPML will treat each subsite independently. This setup means that you can have WPML only on the example.com/en-us/ subsite without causing direct conflicts with the main site that does not use WPML. However, it's important to note that you will not be able to connect content between different subsites using WPML. For more details, you can visit our documentation on multisite support: WPML Multisite Support.
If this solution does not fully address your concerns, or if it seems outdated or not applicable to your specific 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. Additionally, feel free to open a new support ticket for personalized assistance at WPML Support Forum.
Problem: The client needs to export the WPML configuration and is encountering a 403 Forbidden error when trying to access the XML file via Multilingual Tools. This error typically indicates that the server understands the request but refuses to authorize access, possibly due to server permissions, security settings, or firewall rules. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Temporarily disable all non-essential plugins, keeping only the required WPML plugins active. 2. Switch to a default theme, such as Twenty Twenty-One, to rule out any theme-related issues. 3. If the problem persists, consider installing your site on a local server (e.g., using LocalWP or XAMPP) to determine if it’s a hosting-related problem. Please ensure to back up your database before making any changes.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
