Problem: You are trying to ensure that translated pages in French Canadian display the same images and strings as the original version, specifically for header and footer logos and social media text stored as ACF fields on an Options Page. Despite setting the field group to 'Expert' mode in WPML, registering fields as strings, and applying the 'Copy' setting, the French Canadian version returns NULL for image IDs. Solution: First, ensure that WPML creates an image for each language with a proper ID by navigating to WPML > Settings > Media Translation and clicking "Start". Allow the dialog to complete without closing the tab, as this scans the media library and creates any missing entries in second languages.
If the issue persists, it might be due to the ACF option field copying the original ID incorrectly. Go to your Options page, switch the language in the top admin bar, and edit the logo ID using the correct ID for the translated logo. Set the ACF field to "Copy once" in "Expert" mode or set the whole group to "Different fields across languages". To find the translated logo ID, switch the language in the media library, open the logo, and check its ID.
If these steps do not resolve your issue, or if the solution becomes outdated, we 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to find or translate certain hardcoded strings within their theme, specifically in a template partial registered as an ACF block, despite running theme and plugin localization.
Solution: We recommended the client to: 1. Ensure they have a full backup of their website and database. 2. Perform these steps preferably on a staging or development site to avoid issues on the live site. 3. Update WordPress to the latest version. 4. Deactivate all plugins except for WPML and its String Translation add-on. 5. Scan the theme again and then search for the strings in the String Translation section.
Also make sure that for your custom hard-coded texts, these are using proper gettext() methods like _e() or __().
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your specific case, we highly recommend opening a new support ticket. Please also 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. For further assistance, you can contact us directly at the WPML support forum.
Problem: The client is unable to update the site key for acosta.ca to a unique one, as it auto-completed with the site key from another site, acosta.group. Attempts to update or unregister the site key were unsuccessful, with errors indicating a mismatch or invalid site key. Solution: If you're experiencing issues with updating or registering your site key for WPML, we recommend the following steps: 1) Visit the WPML account websites page. 2) If the site URL is already registered, delete it from the list. 3) Re-enter the site URL to generate a new site key. 4) Click on "Show key" and copy the new site key. 5) Navigate to Plugins > Install > Commercial (tab) in your WordPress dashboard, and enter the new key to re-register WPML. If WPML is still registered, de-register it first.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client activated WPML Multilingual CMS and encountered a 403 Forbidden error on the Setup page, despite having the correct file/folder permissions and REST API enabled. Solution: We recommended the following steps to identify and resolve the issue: 1. Create a full website backup. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue persists. 4. If the issue does not persist, reactivate the plugins one by one to identify the problematic plugin. 5. If the issue persists even with non-WPML plugins disabled, switch to a default WordPress theme like TwentySeventeen and check again. We advised performing these steps in a staging environment if possible.
If this solution does not resolve the issue or 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. If the problem continues, we highly recommend opening a new support ticket at WPML support forum.
