Problema: El cliente intenta traducir campos personalizados avanzados (ACF) y, aunque los ha traducido en las traducciones de cadenas, en el frontend siempre se muestran en el mismo idioma.
Solución: Si estás experimentando esto, recomendamos que realices la traducción desde el editor de traducción. Este proceso solo es necesario hacerlo una vez, ya que las traducciones de las opciones se almacenan en la memoria de traducción. Hemos creado un video tutorial para guiarte en este proceso: Video tutorial para la traducción de ACF
I recently found an issue with my site when trying to set up a staging site. I use different domains for different language, and it appears the primary domain and public_html are set as different sites.
From Siteground:
The main domain of your account(Site Tools) is -> your-domain.jp
The parked domain is -> your-domain.co.uk
The site in the public_html is configured to work/load as your-domain.co.uk:
What is the best/easiest solution to this problem?
Solution:
When setting up the Language URL format for A different domain per language, you must follow our guide here.
The server and DNS settings must be correctly applied to make it work. Those are not settings in WPML.
In your case, your-domain.co.uk should be your site's main domain associated with your site's default language language. All the other domains, including your-domain.jp, should be the alias of the main domain, according to how we explain in the guide.
I can't tell why you see it otherwise in Siteground's settings. You should make sure the settings are correct. Also, consult Siteground's support about it.
Problem: The client has an issue with a custom post type in WordPress. After renaming the custom post type from
news_release
to
news-release
, the connection between English (EN) and French (FR) posts was lost, and the posts started to appear as duplicates in the database.
Solution: We recommend the following steps to resolve the issue: 1. Create a complete backup of the site and database. 2. Clear the Cache in WPML. 3. Remove ghost entries from the translation tables. 4. Fix
element_type
collation. 5. Fix WPML table collation. 6. Set language information. For more detailed instructions, please refer to our troubleshooting documentation here: WPML Troubleshooting Options.
If this solution does not seem relevant to your issue, please open a new support ticket in our WPML support forum.
Problem: The client wants to know how to translate products using a CSV file to upload them in two languages. Solution: We recommend using WP All Import and following the steps in our documentation. It's important to adjust the CSV files as described and import products for the default language first, followed by the second language. Ensure that all taxonomies are created and exist before importing. Please check the following documentation:
Problem: The client was unable to disconnect translations from the default language page or post, even after following the steps provided in the WPML documentation.
Solution: We acknowledged that this was a known issue which has been resolved in the latest version of WPML (v4.6.8). We recommended that the client should first take a backup of their site and then update WPML to the latest version to resolve the issue. The update can be done from the WordPress admin area by navigating to Plugins >> Add New page, clicking the Commercial tab, and then clicking the "Check for updates" button.
Problem: The client has migrated their website from a test environment to a production environment and is now seeing a WPML message indicating that the site has been moved. The client wants to keep both the test and production environments working but separated, and is looking to use the "Mark the Original Site as a Copy" option which is not visible. Solution: We recommend updating the WPML plugins to the latest version to access the "Mark the Original Site as a Copy" feature. Here are the steps to update the plugins: 1. Navigate to the Plugins → Add New page on your WordPress dashboard. 2. Click on the Commercial tab. 3. Click the "Check for updates" button. See screenshot Before updating, ensure to create a backup of your website as a precaution.
If this solution doesn't look relevant or if you need further assistance, please open a new support ticket.
Problem: The client is trying to use a custom taxonomy to filter posts and needs to translate this taxonomy, but encounters an 'invalid' error message.
Problem: The client wants to set up a popup form that changes based on the user's GEOIP location. Solution: We recommend contacting the support team of the form plugin being used, as WPML does not provide GEOIP-based functions to determine the user's current country.
Problem: The client is experiencing an issue where the translated Helpie FAQ section is not displayed on the German version of their website. Solution: We have tested the Helpie FAQ plugin and found a solution to display the translated FAQs on the translated page. The client needs to translate the FAQs, and associated Categories and Groups to ensure they display correctly in other languages. We have created a detailed video tutorial to guide the client through the process step by step. We recommend watching the video to understand how to implement the solution: http://tinyurl.com/ynyh9fdj We are confident this will resolve the issue and are looking forward to the client's feedback. If this solution does not seem relevant or if further assistance is needed, please open a new support ticket.
Problem: The client requested documentation for using WPML with WP Recipe Maker, specifically for translating recipe instructions and ingredients. Solution: We recommend reviewing the solutions from existing tickets that address WPML's integration with WP Recipe Maker. You can find these solutions by visiting the custom search URL we've created:
These resources should guide you through the process of translating your recipe content. If you find that the solutions provided do not address your specific issue, please do not hesitate to open a new support ticket with us. WPML Support Forum
Problem: If you're trying to update WPML modules such as WPML Media, WPML Multilingual CMS, and WPML String Translation, but encounter an error stating 'WPML Multilingual CMS cannot update because your site's registration is not valid. Please register WPML again for this site first.', follow the steps below. Solution: 1. Verify your WPML key and the domain used for that key on your WPML account page. 2. Provide temporary access to your site (wp-admin and FTP) to the WPML support team, ensuring you have a full backup of your site before doing so. For privacy and security policy, refer to this link. 3. After providing access, the WPML support team will attempt to register WPML using the key you provided and check for updates. 4. If successful, WPML and its add-ons will be updated to the latest version. 5. If you see a notice stating 'WPML plugin cannot connect to wpml.org', it may be a false positive due to local or server caching and should resolve itself when the cache clears.
Problem: The client is trying to set up WPML on their website, which is in Spanish, but the content is in English. They need guidance on how to configure the default and secondary languages. Solution: We recommend deciding which language you want to appear as the default when visitors access your site. Here are the steps for both scenarios: 1. If English is to be the default language: - Set up WPML with English as the default language and Spanish as the secondary language. - No additional steps are required; you can start translating from English to Spanish. 2. If Spanish is to be the default language: - Set Spanish as the default language and English as the secondary language in WPML. - Copy the current English content to the secondary English language to avoid losing it. Use the following documentation to assist you:
- After copying, update the current Spanish content (which is in English) to actual Spanish. The second option requires more effort, but both are viable depending on your preference for the site's default language.
If this solution doesn't look relevant to your situation, please open a new support ticket and we'll be happy to assist you further.
Problem: The client is having difficulty finding and setting up the Mexican Spanish language pack for their development website. Solution: 1. To add the Mexican-Spanish language (es-MX), use the URL at the bottom area inside your screenshot to create a custom language. 2. Follow our documentation on how to add a custom language, which provides step-by-step instructions. 3. If you're planning to use automatic translation, ensure that your language code is supported by referring to the list of supported languages for automatic translation. 4. Since Mexican Spanish ("es-MX") is not supported for automatic translation, you can map this custom language to a supported language, such as "Spanish", to use automatic translation features. 5. For more details on using automatic translation with a custom language, check out our documentation on automatic translation with custom languages.
If this solution doesn't look relevant to your situation, please open a new support ticket so we can assist you further.
Problem: The client's site, originally in German, was incorrectly identified as an English site, which led to the unnecessary use of over 8,000 translation credits to "translate" the text back into German, essentially duplicating the existing content. Solution: We recommended that the client disconnect the German pages from the English ones by setting "this is a translation of none" in the WPML settings. After this, the client should change the language of the page to German. Once that is done, they can proceed to translate the German page into English. If you're experiencing this issue, we recommend you follow these steps: 1. Disconnect the German pages from English by setting "this is a translation of none". 2. Change the language of the page to German. 3. Translate the German page to English. If you encounter any problems with the translations, please open a new support ticket and we will be happy to assist you.
Problem: The client wants to change the original translation language from Dutch to English and is having trouble seeing the English text when translating to Polish, even after changing the primary language of the site. Solution: If you're experiencing issues with changing the original language for translation, we recommend the following steps: 1. Instead of using the 'Automatic Translation' feature in WPML > Translation Management, choose the 'Translate myself' option. 2. Then, navigate to WPML > Translations and select 'Translate' for the content you wish to work on. 3. If you're not translating in bulk and can manage content one by one, this method will allow you to translate from the new source language. 4. For bulk translation, please note that our team is currently working on this feature, and we do not have a specific timeline for its release. 5. As a workaround, you can create content in the desired source language by switching to that language in the backend before creating new content. This will set the new content's source language accordingly.
We also provided a detailed example using a test site where the default language was changed, and content was created in the new source language to facilitate translation.
If this solution doesn't look relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
