jordanP-2

Problem:
If you're working on a site and trying to configure the Theme Option for the footer in the Spanish language, but it's not functioning correctly, here's what we found and how we addressed it.
Solution:
1. We noticed that ACF Option Pages should not be translatable. In your WPML settings under WPML > Settings > Post Types Translation, set the translation preference to "Do not translate."
2. There were duplicated field groups for the same footer option page. We deactivated the unnecessary one and renamed it to "Option page: Footer inactive."
3. The translation mode on the footer group was initially set to "Different fields across languages." We recommend changing this to "Same fields across languages" to ensure consistency across translations.
4. The persistent error was due to a corrupt Spanish translation. To resolve this, we duplicated the field group and deactivated the original. The new active group is now "Option page: Footer (copy)."
You can now access the English footer option page, save it, and switch to Spanish to translate your content.

Please note that this solution might be 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. If the issue persists, please open a new support ticket.

Problem:
The client is creating a new website using WordPress and wants to use WPML to manage different versions for the US and UK. They are concerned about the URL structure because the language code 'uk' is typically used for Ukrainian, and they want to use it for the UK version of their site.
Solution:
We recommend not altering the WPML languages table to change the Ukrainian language code to something else and then creating a custom language for 'uk'. This is because 'uk' as a language code for Ukraine is an international standard. You can use "en" or "en-gb" for Great Britain. For the US version, you should use the custom language code "en-us".
Using incorrect language codes can negatively impact SEO by causing incorrect targeting, poor user experience, duplicate content issues, and hreflang tag errors. To avoid these issues, ensure you use the correct language codes and implement hreflang tags properly. This will help search engines understand which version of your content to show based on language and location.
For more details on setting up custom languages, visit:
WPML Custom Languages Setup Guide
For information on country codes, refer to:
Country Codes Reference

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket.

Problem:
If you're experiencing a 404 error when switching the language from English to Spanish on your site, it might be due to a conflict caused by having the same custom rewrite slug for both your taxonomy and your Custom Post Type (CPT).
Solution:
We recommend that you navigate to CPT UI > Registered Types and Taxs, then edit both the CPT and taxonomy to remove the custom rewrite slug. After making these changes, ensure to clear your Pantheon cache. This should resolve the issue and allow you to view the taxonomy page in Spanish as well.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at WPML support forum.