Skip Navigation

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.

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by Prosenjit Barman 1 year, 10 months ago.

Assisted by: Prosenjit Barman.

Author Posts
August 9, 2023 at 1:15 pm #14175875

angelinav-2

Hello,
I'm having the same issue I had June 14th, then this solved the issue:

1. Go to WPML > Support.
2. Click on the Troubleshooting link.
3. Click on the "Fix post type assignment for translations" button.
4. Click on the "Remove ghost entries from the translation tables" button.

--

But unfortunately this doesn't do the trick now... it's the same:

I get a critical error using the plugin WPML Multilingual CMS. I got this message (see image) and also within the error logs it says some errors (see also image).
And when I try to translate the pages it doesn't do anything.. this is the website: hidden link

Scherm­afbeelding 2023-08-09 om 15.14.43.png
Scherm­afbeelding 2023-08-09 om 15.14.15.png
Scherm­afbeelding 2023-08-09 om 15.13.23.png
Scherm­afbeelding 2023-08-09 om 15.13.17.png
August 9, 2023 at 2:11 pm #14176591

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There,
Thanks for contacting WPML Support. I will try my best to assist you in this matter.

I check the screenshots that you've shared and understood the issue. It seems certain elements within the site's database have become corrupted, which appears to be the primary cause of the issue. I kindly request you to apply the solution mentioned in the Errata below and check if that helps to solve the issue.

- https://wpml.org/errata/fatal-error-invalidargumentexception-element_id-and-type-do-not-match/

Please take the database approach mentioned in the Errata and delete the rows from there accordingly.

Let me know if that helps or if you need further assistance in this matter. I will be happy to help.

Best Regards,
Prosenjit

August 9, 2023 at 2:24 pm #14176685

angelinav-2

Okay! I will try by the database approach. Where can I find the 'element_id' for the error?

August 9, 2023 at 3:22 pm #14177157

angelinav-2

Update: I also reached out to my hosting, they said it was an issue within the htaccess file. They said it was because sometimes some plugins make changes within this file. They changed it and the websites works again. 🙂

August 10, 2023 at 10:11 am #14181065

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There.

Happy to hear that the site is working again after changing the htaccess file.

However, if you ever encounter such a situation again, you should check the debug log(Steps to enable the debug log in mentioned here: https://wpml.org/documentation/support/debugging-wpml/) and take steps accordingly. If the error is caused due to a corrupted element, you should see the `element_id` there.

Note the "element_id" and follow the steps mentioned in the Errata I shared in my previous response.

Let me know if there is anything else you need help with. I will be happy to assist.

Best regards,
Prosenjit