[Resolved] the connection with the original language of the post gets lost
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing an issue where adding a translation to a blog post or page using the Gutenberg editor causes the connection with the original language of the post to be lost, resulting in it being listed as a separate post in that language. Solution: Updated WordPress, and plugins solved the issue.
This solution might be irrelevant if it's outdated or not applicable to your 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 continues, please open a new support ticket at WPML support forum for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
hello, I noticed sometimes there is this WPML-related bug on our website, basically when a user adds a translation to a blog post / page using the Gutenberg editor, the connection with the original language of the post gets lost and it will be listed as a separate post of that language
hello,
I followed exactly the steps you described and the issue is still there.
I tried to add a german translation clicking the + icon (from Editor itself AND posts list as well) and I get the german post separated and not connected with the original english post.
Thanks for trying those steps. This issue might be due to some possible theme/plugin conflict on your site. Could you please follow the below steps and see if this resolves the issue:
1. Please take a backup of your site first for safety reasons.
2. We have recently released WPML 4.6.11, please update it to the latest version.
3. Please make sure to update all outdated plugins/theme to the latest version and see if this resolves the issue.
4. If the issue persists, kindly perform the following steps to isolate the cause of the issue:
- Deactivate all plugins except WPML and it’s add-ons.
- Switch to the parent WordPress theme like 2023.
- If the issue is gone, reactivate each plugin one by one to identify the one causing the issue.
5. If the issue still persists, please provide temporary access (WP-Admin and FTP Login info) to your site (preferably staging site), so that I can look into your setup and debug the issue.
Your next answer will be private which means only you and I have access to it.
=== Please backup your database and website ===
✙ I would additionally need your permission to deactivate and reactivate Plugins and the Theme and to change configurations on the site. This is also a reason the backup is really important.
hi,
I've just updated eveything, WordPress and rest of the plugins included, and WPML 4.6.11 as well and now I can't replicate anymore the issue.
I wonder if this was a bug in the WPML plugin and it got fixed in the latest WPML update.
I guess we'll never know for sure.