Problem:
WordPress found a fatal database error on the Website that looks this way:
COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’
Solution:
The reason for this issue is that various database tables use a different collations.
To solve the issue a matching and similar collation for all DB tables.
You can run the following MySQL query to solve such an issue, but it will need to be adjusted with the matching table prefix and also in case a different collation is used than mentioned inside the query:
ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
Problem:
On the translated pages in English, the links are pointing to the original Dutch pages instead of the translated English pages.
Solution:
You need to translate the page and finish the translation job.
- Go to WPML->Translation Management-> Send the page for translation and then take the translation job.
- Translate 100% and save.
Problem:
My problem now is that I want to add en-GB as a language. When I try to add English with a code of 'uk' I get an error that 'The Language code already exists.'. I assume this is because the database is pre-populated with Ukraine as a language. This is not unreasonable, but people in the UK often refer to the country as UK not GB, and even if I could change my folder for UK English to be GB it is pre-existing as UK, so this would cost me in SEO which I cannot accept.
Solution:
Deleting a language from WPML is not a good idea.
Instead, you can go to WPML → Languages → Site Languages, press the Add / Remove languages, add the Ukraininan language, then press the Edit Languages link. This way you'll be able to "transform" Ukrainian into UK English.
Problem: We are using the Salient Theme and our problem is that the link of the button module of the vpbakery implementation is not pointing to a translated site but to the original
Solution: I added the following code in WPML -> Settings -> Custom XML Configuration tab:
I would like to ask you to follow these steps:
- Go to WPML -> Settings -> Activate Classic Translation Editor
- Edit the test page in German -> Make a small change in the content -> Save the changes -> Update the translation.
Problem: Unable to access the sub sections of WooCommerce My Account page in secondary language
Solution: This issue is happening because there are limitations to use different slugs for WooCommerce Endpoints. It works after the following steps. Please try it after a full site backup.
1) Go to Woocommerce>>Settings>>Advanced
2) Scroll down to the endpoints section and save
3) Go to WPML>>String Translation
4) Choose *WP Endpoints* option for *Select strings within domain* drop-down box
5) Delete the WP Endpoints strings registered in Arabic
6) Mark the translation of English WP Endpoints as *Not translated*
7) Visit Settings>>Permalinks and resave the settings
Problem:
When moving between months, the url now looks like this:
domain.com/(/?:events)/(/?:month)/2020-05/ when it should look like domain.com/events/month/2020-05/
Solution:
Events Calendar takes the translation of months from WordPress language files. If you have those translation downloaded, month and day strings will be loaded from those files. Otherwise, you can delete language files and translate months using WPML.
I've checked things on your site and found out that the problem is coming from one of the files in the following location:
/wp-content/languages/wpml/
Please proceed as follows.:
1. Take a backup of your site in case something goes wrong so you will be able to restore things before the following changes.
2. Connect to your site with FTF or use the WP File Manager plugin that is installed on your site. And go to /wp-content/languages/wpml/.
3. Select all the files in this folder and delete them.
4. Visit WPML -> String Translation. This should generate new files in /wp-content/languages/wpml/ and fix the problem.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
Problem:
When translating a page, it includes content that doesn't exist on the page. Upon investigation, I found that this is content that was added to the native WordPress editor. Upon switching the editor to Divi Builder, it saves it in the background, so it can be restored when you disable the Divi Builder again.
The problem is that WPML also sends this old content to the translator, who will then translate and charge for it. I can't find a way to get rid of it from within WordPress/Divi, so was hoping there is a way to exclude it from being send to the translator.
Solution:
The field that you're looking for is _et_pb_old_content.
I'm not sure if this field is needed by the Divi builder or not, but I went to WPML → Settings → Custom field translation, searched for this field, pressed the lock icon to be able to change its settings, and set it to copy (just to be safe).
Now, I went back to the page I created (in the original language), just hit the Update button (without opening the page in Divi builder), then updated the translation. This time, the field-_et_pb_old_content didn't appear anymore.
2. Please make sure that you first create a full website backup so that you are safe no matter what happens.
3. The oldest version you are able to download from that link is "3.8.3". After that, I recommend that you update to each new major version (3.9, 4.0, 4.1, 4.2 and 4.3).
You can also try to create a full website backup first and then update to the latest version and see what happens - it there's gonna be serious errors and not simple notifications, then please update gradually.
Make the attribute copy/copy once/translate in WPML > Settings > Custom Term Meta Translation. screenshot attached.
Please go to WooCommerce -> WooCommerce Multilingual -> Attributes. Here, select your attribute and then click "Sync attributes and update product variations". Does this resolve the issue for you?
If not, please go to WooCommerce Multilingual and click on the Status tab. Scroll down and click the troubleshooting link. Then run through the troubleshooting steps. Does this resolve the issue?
Please be sure to make a full backup of your site and database.
Then, go to WPML -> Support -> Troubleshooting.
Look for 'Clean up' and click the following:
- Synchronize posts taxonomies (run this once for Variations and once for Products)
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix Terms count
- Fix post assignment for translations
After these steps, do the Product -> Attributes should show the correct counts.
If you are making changes to the number of languages your site is available in, you can delete all languages except for the default one. This action also removes the translations for the deleted languages from your site and database.
If you additionally want to uninstall WPML, you can do a WPML reset. This removes all remaining WPML tables from the database.
Problem:
The main domain is mydomain.be. The second domain is mydomain.com. My objective here is: when people are in Dutch, they see the .be site. When they're in English, they see the .com site.
Solution:
Set up both domains to point to the same server IP address and the same directory where WordPress is located. Alias configuration should all point to the same physical folder where your WordPress is being installed. URL should show the same website.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive