This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported not receiving replies to their tickets and described an issue where the Classic Editor interface was not consistent across all pages, with Elementor sections lumped into one block. This problem occurred only on some pages. Additionally, there was a database error indicating a missing table ('rai_e_notes') related to Elementor Pro's Notes module, and a React error in WPML's files. Solution: We recreated the issue and confirmed it does not occur on newly created content. A temporary workaround involves using a plugin like Duplicate Page to duplicate existing pages. For the database error, we suggested reinstalling Elementor PRO or manually recreating the missing table, and consulting Elementor Support for further assistance. For the React error, we recommended updating all plugins and testing again. If the issue persists, further investigation is necessary.
Please note that this solution might be 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 persists, please open a new support ticket.
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.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Thank you very much!
I was able to access the site and server now.
I have now disabled Elementor on your site and you will see for example on your Hompage that the content is still there. The content here was saved inside a Classic Block.
I have used now the option "Convert to blocks". Then I enable Elementor again and opened the WPML Translation Editor.
It seems that this has solved the issue. Please verify.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
About the error:
It looks like the website used to use the language code en-usa and there was still translation data on WPML's tables on the database using this language code.
I have removed those entries now, which should resolve the error.
---
About the duplicated content issue:
Please provide me with more background to understand how the issue occured.
Was the content earlier created using the Classic Editor or Gutenberg and Elementor was added later on?
It appears to be working now. Content was always created with Elementor and then translated with WPML.
What did you do with the language code en-usa? Can you send a video of what you did so it can be replicated? Or can you do the same on the live site? You already have access to the live site.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I can not send identical screnshots, because the entries are alreayd deleted.
If you edit the database with a tool like PHPmyAdmin you will need to edit the table:
wp_icl_translations
Here search for entries that use inside the column language_code or source_language_code:
en-usa
Delete this entries. As I recall correctly you might not need to adjust any further tables, as the entry I found did not even have a post_id (which is similar to element_id), which means it did not longer exist on the wp_posts table. It was likely a leftover from old translations.
You should also be able to find the entries, if you filter the colomn "element_id" for an entry with NULL.
I can still offer to fix this issue on your live site, if you would like to provide access.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
When it comes to WPML I would not say that this would be necessary, but if the Elementor Staff recommend this due to the Elementor Errors on the site, then maybe it might be recommendable.
I can offer to revise the live site for you. The private reply form is enabled again, in case you would like me to take a look.
