Problem: The client was experiencing issues with WPML updates failing due to the hosting server's inability to whitelist certain domains necessary for the updates. Solution: We recommended that the client ask their hosting provider to whitelist the domains: wpml.org, cdn.wpml.org, and api.wpml.org. Additionally, updating OpenSSL on the server might resolve the issue. If the hosting provider is unable to whitelist these domains, we suggested manually updating WPML by downloading the latest versions from https://wpml.org/account/downloads/ after creating a full website backup and removing the existing WPML plugins. Alternatively, changing the hosting provider could be considered.
If this solution does not apply to your situation, 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 at WPML support forum for further assistance.
Problem: The client is experiencing issues with currency shifting and stock updates on their WooCommerce site when NitroPack caching is enabled. The currency selection is supposed to be based on the client's country, but it sometimes fails to change correctly. Additionally, product stock levels are not updating as expected. NitroPack support inquired about the use of variation cookies related to the WooCommerce Multilingual plugin, which the client could not find in the session.
Solution:
1) We confirmed that the necessary cookies for handling languages and currencies already exist, and one of them is a NitroPack cookie.
2) We invited NitroPack to collaborate with us through the Go Global Program to ensure compatibility between our plugins.
3) We provided a code snippet to create a custom cookie for currency:
4) We advised the client to add this code to their functions.php file and to ask NitroPack how to exclude the 'wcml_custom_currency_cookie' from caching.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to register WPML on their WordPress site and has followed the step-by-step instructions but is experiencing issues.
Solution: If you're experiencing issues with registering WPML on your site, we recommend you try the following steps: 1. Log in to your WPML account and go to the Sites page. 2. Delete the existing site key. 3. Create a new subscription key for your site. 4. Visit your Site Dashboard and navigate to Plugins >> Add New >> Commercial tab. 5. Click on the “Unregister WPML from this site” or “Register” button. 6. Register with the new site key and refresh the page.
For more detailed instructions, please refer to our documentation:
Problem:
I read quite some threads about this topics already, but I am still not sure what is the best option to use in my situation, could you help me?
Some basics:
- We have an English website with a lot of content.
- We want to translate only a part of it (e.g 30% of the pages) into Spanish
- We want to use Advanced Translation Editor
- We use Elementor page builder
So we should be able to:
1. Translate full pages from English into Spanish with the Advanced translator Editor
2. Once a page is translated, go to the Spanish page in Elementor page builder and make some modifications (e.g remove a section or links to pages that don't exist in Spanish. Since only a part of the Website is translated, some sections are linking to non existing content in Spanish and we should remove them.)
3. In the future, when the original English page is updated, we should be able to translate these modifications via the Advanced translator Editor into Spanish.
Solution:
In this case, the best alternative is to translate the content manually. Therefore, it would be Option 3: Duplicate and "Translate independently".
If you use the Translation Editor to translate the content, edit the Spanish version with Elementor to have a different design, it'll be overwritten when you make a modification in the original page, and update the translation. You can check by yourself this behavior:
- Translate a page with Advanced Translation Editor or Classic Editor
- Edit manually the translated page with Elementor
- Make a small change to the default page
- Update the translation and check that the edition you made will be overwritten with the original page layout
So, in order to avoid this and use manual translation, please follow these steps:
- Open the page/post you want to translate manually
- In the Language box, turn off WPML’s Translation Editor switch found in the ‘Translate this Document’ section
- In the 'Use the WordPress Editor to translate' pop-up dialog that appears, select 'This page' option
- In the Language box, select the Duplicate checkbox, and then click Duplicate. This will duplicate the page in the selected secondary language
- Click on the pencil icon to edit the page in the other language
- On the editing page of the duplicated page, click 'Translate independently' in the Language box
Some themes, like The7 theme, allow you to set logos via theme options.
If you want to use a different logo per language, you need to translate the logo ID in String Translation. This tells WPML which logo to display in each language.
If you cannot find the default language logo ID on the String Translation page, you can click the Translate texts in admin screens link to add it to the String Translation table.
Problem:
Learndash courses disappeared from the frontend after updating to WordPress 5.8
Solution:
The debug log file showed the following error:
1
PHP Fatal error: Uncaught InvalidArgumentException: element_id andtype donot match forelement_id:42 the database contains post_attachment whilethis functionwas called with post_post in xxxx/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-set-language.php:34
And it was fixed with the following steps:
Go to WPML > Support > Troubleshooting page, then click these options:
- Clear the Cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Fix WPML table collation
- Set language information
Problem: If i don't use a translation editor and i want to have different flexible field elements per language, some of them erase their content
Solution: set the translation preference of all the fields inside the flexible field to either "translate" or "copy once". They all MUST have the same exact translation preference (included the flexible field itself).
Problem: MotoPress Hotel Booking Calendar not showing
Solution: It looks like a compatibility issue and translated Accommodation post ID is not synced in Spanish Pages. It works as expected when we specify the ID of translated Accommodation post. So we have to manually translate the Accommodation post ID in translated pages to fix this issue.
But the issue is still there, the code made no difference. The error doesn't appear on the staging server.
Solution:
We could solve the icl_table issue in your website following these steps:
- First, we excluded WPML plugins and reinstalled with their latest versions
- Then, we removed the code on functions.php that you've added in order to recreate the icl tables
- We went to your database and could find the entries "wpml_string_table_ok_for_mo_import" and "wpml_notices"
- After we deleted them, the issue was fixed and the notice on your WP Dashboard disappeared
Problem:
I translate the page and save the translation, but when I go to a page for that language i.e. http://example.com/en/about-us/ the content of the header is still the default.
Solution:
First of all, please go to WPML → Settings → Custom XML Configuration tab and add this XML config to it:
Here, edit the Permalink and change fmt-header to fmt-header-es (just simply add -es at the end, so the permalink in each language can be different).
The last step is to go to WPML → String Translation and search for the header template permalink. In the test website is fmt-header. As the translation, just simply add the permalink that you just set, fmt-header-es.
This time, when checking a page in the secondary language, the translated header will be used: https://website.com/es/
Problem:
In WPML - Settings - Custom Fields Translation, many fields are linked to a plugin that no longer exists, but still many Fields are present. How to remove them?
Solution:
WPML doesn't know once you remove a plugin. All fields are still active in the DB and therefore, WPML still displays them. Please refer to the following post, which explains this perfectly for ACF Custom Fields.
In the "Pricing" section of the widget, I set the Currency Symbol to 'None', and (optionally) added a $ to the 39.99 price. Is there is a way to get WPML to include the price text field for translation via Translation Editor, along with the Heading, Period, Button Text etc?
Solution:
- Go to WPML > Settings > Custom XML configuration and add next XML code:
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
