Problem: The client is experiencing an issue when trying to send translation jobs to Crowdin using WPML. The error message received is 'Sending for translation failed. The jobs could not be created.' This occurs when selecting a page for translation and setting the method to 'assign translation service'. Solution: 1. Ensure that the language mapping is correctly set up in Crowdin. Go to Crowdin's project settings, navigate to the Languages section, and click on the Language Mapping button. Create a rule for the Spanish language with the placeholder 'locale' and the custom code that matches WPML's code for Spanish. 2. After setting up the language mapping, attempt to create a translation job again. 3. If the issue persists, check the communication log in WPML by navigating to WPML->Support and clicking on the communication log link. Share this log with us for further analysis. 4. Test with a new sample page containing just a title and one line of text to see if the issue is specific to certain pages or posts.
If this solution does not resolve your issue or seems outdated, please 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. If problems persist, we highly recommend opening a new support ticket for personalized assistance.
Problem: If you're experiencing major loading issues in the WordPress admin dashboard when logged in, and the site speeds up when WPML is deactivated, it might be related to the version of WPML you are using. Solution: We recommend updating your WPML plugins to the latest version, as this issue should be resolved in WPML 4.7. If after updating, the problem persists, please check our known issues page and verify that you have installed the latest versions of your themes and plugins.
If the solution provided here does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. You can do so by visiting our support forum.
Problem: The client is working on a site under development and wants to change the custom post type (CPT) label to the Korean language. Solution: If you're trying to change the custom post type label to Korean, we recommend using the WPML String Translation module. First, ensure that you have scanned all related plugins for translatable strings in WPML > Theme and Plugin Localization. After scanning, go to WPML > String Translation and search for the CPT name. You can then add the translation directly there. For more detailed guidance, please check our documentation for developers at https://wpml.org/documentation/support/.
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 this does not resolve your issue, please open a new support ticket at our support forum.
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: You are experiencing login errors on the .co.uk URL and encountering 404 errors when using the WordPress preview option on the same domain. Additionally, you asked about setting different time zones by language. Solution: The issue with the login and preview errors is recognized and has been escalated to our developers. However, it is not a high priority fix due to its infrequent reporting, and there is no estimated time for resolution. As a workaround, ensure you are logged in on both the .com and .co.uk domains. You can verify this by checking for the admin bar on the frontend. If it's not visible on the .co.uk domain, log in again at
/wp-admin
on .co.uk, and you should be able to preview pages normally.
Regarding setting different time zones by language, this needs to be configured on a user-by-user basis.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
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: You are developing a site and are trying to translate button text into other languages using WPML, but are unable to change the button text in other languages. Solution: We found that the text was coming from a button of an ACF field group. The field group translation method selected was 'Same field across languages' but you are manually translating the page. To resolve this, go to ACF > Field Groups and search for the group containing that button: 'Media with Content Block'. Edit it and select the 'Expert' mode. Then find the button field and mark it as 'translate'. After that, edit the Spanish translation of the page and you should be able to translate the button 'View Products' to 'Ver Productos'. Check the front end to see if it displays correctly.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, 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.
Problem: You are trying to understand what 'Default Locale' means in the Languages setting page of WPML and whether it needs to match the hreflang. Solution: The 'Default Locale' option in WPML helps pull the translation strings from WordPress translation systems for themes and plugins that are translated there. You can check and set the correct locale for your site's language at https://translate.wordpress.org/. It is important to note that the 'Default Locale' does not need to match the hreflang option. For more information on adding hreflang, please follow our documentation at https://wpml.org/documentation/support/adding-hreflang-wordpress/.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client needed to adjust hreflang tags for
different regional versions of their website. Specifically, they wanted to
change 'en-usa' to 'en-us' and set regional codes like 'en-x-emea' and
'en-x-apac'. Additionally, they encountered issues where changes were not being
saved and received an error stating 'The hreflang already exists.'. Solution:
We advised that the hreflang formats like 'en-x-emea' or 'en-x-apac' can be set from WPML -> Languages by adjusting the hreflang as needed.
To resolve the issue of the hreflang not saving (because the Enlgish language was used before, and as a result the hreflang "en-us" was already set to it), we suggested:
1. Activate the default English language on WPML -> Languages.
2. Change the hreflang for the default English language if it was previously set to 'en-us'.
3. Save the changes.
4. Attempt to change the hreflang from 'en-usa' to 'en-us' again and save.
5. Remove the default English language on WPML -> Languages if no longer needed.
This process helped in correctly setting up the desired hreflang tags. If these steps do not resolve your issue or if the solution seems 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with their sitemap displaying pages that do not exist, specifically URLs containing "/en/" which were remnants of an old language setup. The client had already tried resetting Yoast sitemap and indexables without success.
Solution: We recommended the following steps: 1. Re-enable English as a language temporarily in WPML > Languages. 2. Manually delete all media, pages, custom posts, taxonomies, and menus associated with English using the WordPress User Interface and the language switcher. 3. Remove the English language again and run the cleanup dialog. 4. Check WPML > Settings > Post Type Translation to ensure that any post types that should not be translatable are set correctly. 5. If necessary, temporarily set certain post types (like ACF Field Groups) to 'Translatable' to delete specific entries, then revert them to 'Not translatable'. 6. Run a MySQL query to clean up leftover entries in the database:
DELETE FROM `wp_icl_translations` WHERE `language_code` = 'en'
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
