Problem: You are unable to send content for translation using the latest WPML plugin. Solution: First, ensure that your user account is assigned as a translation manager. This is crucial as having multiple translators and translation managers can sometimes lead to permissions issues. For more details on user roles and capabilities, please visit WPML Admin Capabilities. After confirming your user role, please try sending the content again by navigating to WPML → Translation Management.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. Additionally, you can open a new support ticket for further assistance at WPML Support Forum.
Problem: The client wants to modify the batch name on their site using functions.php but is unsure if there is a WPML hook available for this purpose. Solution: We reviewed the client's request and confirmed that there is no existing WPML hook that allows modification of the batch name directly from functions.php. This task requires custom development, which is outside the scope of our support.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem:
If you're experiencing issues with your custom options page created with ACF not showing translated data when switching languages from the dashboard, follow these steps for a solution.
Solution:
1. Navigate to your options page.
2. Switch the language using the top admin bar.
3. Manually add translations to your options fields.
4. Save the translated options page.
Please note that the solution provided might be outdated or not applicable to your specific case. If after following the steps and checking the documentation you still face issues, we encourage you to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact us in the WPML support forum.
Problem: The client has a static home page with a custom plugin that creates a URL structure for different languages. After installing WPML and setting 'fr-fr' as a custom language, there is a permalink error for the French-language homepage. The expected URL is
https://mysite.com/news/fr-fr/fr-fr
, but WPML generates
https://mysite.com/news/fr-fr/
. Solution: We recommend not altering the URL structure that WPML generates, as it is designed to add the language directory after the SiteURL. Interference from custom plugins can cause unexpected behavior. If the client requires a custom solution to maintain the previous URL structure, we advise contacting a certified developer who can assist with this specific need. Developers can be found at https://wpml.org/contractors/.
Problem:
The client needs help adding custom languages English (en-us), French (fr-fr), and Italian (it-it) instead of the predefined English (en), French (fr), and Italian (it).
Solution:
1. If the client needs to change only the hreflang attribute to fr-fr, they can use the default French language provided by WPML and modify the hreflang accordingly.
2. If the client wants to have fr-fr in their URLs (e.g., domain.com/fr-fr), they need to create a custom language. This involves: - Adding the default French language and changing its default locale to something other than fr_FR. - Then, adding the custom language with fr_FR as the default locale. - Finally, deleting the default French language to avoid conflicts. We also advise that it's generally recommended to have a "general" language before regional ones (e.g., fr, fr-be, fr-ca instead of fr-fr, fr-be, fr-ca).
