Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are experiencing a 500 internal error in Elementor, which you believe is caused by WPML.
Solution:
We found that the issue was due to pages in different languages being duplicates of each other, leading to a recurring issue. To resolve this, we recommend deleting all meta keys named

_icl_lang_duplicate_of

from the

_postmeta

table. Please try this solution and confirm if it resolves the issue on your end.

If this solution does not apply to your case, 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 the issue persists, please do not hesitate to open a new support ticket at WPML support forum.

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 1 replies, has 2 voices.

Last updated by Long Nguyen 10 months, 1 week ago.

Assisted by: Long Nguyen.

Author Posts
September 5, 2024 at 6:30 am #16143169

exiliensoft

Background of the issue:
I am experiencing a 500 internal error in Elementor, which I believe is caused by WPML. I am trying to resolve this issue on my site hidden link.

Symptoms:
500 internal error in Elementor

Questions:
How can I fix the 500 internal error in Elementor caused by WPML?

September 5, 2024 at 8:03 am #16143501

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi,

After restoring your site on my local host to investigate the issue, I found the root causes of this. The page in the English language is a duplication of the page in the Dutch language and vice versa, so it leads to a recurring issue. I deleted all meta key "_icl_lang_duplicate_of" from the table _postmeta and the issue is resolved.

Can you please confirm it works on your end?

pro-rotating.clientdemos.app : Signon test : wp_4sgsy : Z9oYf6gR_postmeta | phpMyAdmin 5.2.1 2024-09-05 14-58-14.jpg