Problem:
The client needed confirmation that WPML supports translations over API calls, specifically with custom languages, as this is a crucial feature for their blog. Solution:
We assured the client that WPML does indeed work with translations over API calls and that custom languages function with the same parameters as predefined ones. The only difference is that predefined languages are already set up within WPML. If you're experiencing issues with WPML's API integration or custom languages, we recommend checking that you have the latest versions of WPML, themes, and plugins installed. For further assistance, please feel free to open a new support ticket. We also highly recommend visiting the WPML known issues page to verify if there's a permanent fix for your issue and to ensure you're using the correct version of the fix.
If the solution provided here is not relevant to your case, or if it's outdated, please open a new support ticket for personalized support. You can do so by visiting the WPML support forum.
Problem: The client needed to maintain the existing URL structure when moving posts to WPML, including the use of specific language codes (en_US, es_ES, pt_BR) in the URLs, keeping the category and slug in English for every language, and ensuring the English default language code 'en' appears in the URL.
Solution: 1. To customize the language code in the URL, we suggested using a custom language. Since the same locale cannot exist twice in the database, the client should use a different locale for the custom language or change the locale of an existing default language, then create a custom language with the desired locale. Afterward, the original default language can be removed.
3. For the issue of the default English language code not appearing in the URL, we opened a new support ticket to address the slug translation question separately, as per our support policies.
If this solution doesn't look relevant, please open a new support ticket here: WPML support forum.
