Skip to content Skip to sidebar

Home › Support › English Support › [Escalated to 2nd Tier] Divi dashboard disappears when WPML plugin activated

[Escalated to 2nd Tier] Divi dashboard disappears when WPML plugin activated

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-07:00)

Tagged: 

This topic contains 18 replies, has 0 voices.

Last updated by Bobby 1 month, 3 weeks ago.

Assisted by: Bobby.

Author Posts
October 3, 2025 at 8:38 pm #17455460

Nicolas V.
Supporter

Languages: English (English ) French (Français )

Timezone: America/Lima (GMT-05:00)

Hi There,

While our developers are looking for a fix. Could you please try the following:

- Access your server via FTP and open wp-config.php (in your WordPress root directory).
- Insert this line just before /* That's all, stop editing! Happy blogging. */

define('WPML_DISABLE_PROXY', true);
October 7, 2025 at 12:05 pm #17463640

reneK-43

Sorry for some reason I don't get emails when you reply, although I configured that. I checked a few times but without logging in, then I don't see this answer.

This change seems to solve the issue.

Regards,
René
October 7, 2025 at 11:09 pm #17465581

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi René,

Glad to hear that this resolved the issue!

October 8, 2025 at 6:50 am #17465860

reneK-43

Hi Bobby,

Is this a permanent solution or a temporary workaround?

Regards,
René
October 8, 2025 at 7:19 pm #17468825

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi there,

This is a workaround, at the moment there is no permanent solution as our team is still investigating this, once a permanent solution is introduced it will most likely be included in the next release.

At the moment please use the workaround and we will update this ticket once a permanent solution is implemented.