cneg

Update — issue isolated and working workaround found

I have now isolated the issue much more precisely.

Since my original post, Polylang has been updated from 3.8.8 to 3.8.9, but the issue remains.

I captured the Elementor editor network traffic in a HAR file and found the following:

Elementor sends an AJAX request to:

/wp-admin/admin-ajax.php

with:

action=elementor_ajax

and the batched action:

get_widgets_config

This request does not contain:

pll_ajax_backend=1

The server response already contains Elementor widget controls translated into German, for example:

• Typ
• Beschriftung
• Textbereich
• Auswahlliste

I also found a later Elementor AJAX request for:

get_widgets_default_value_translations

with:

locale=de_DE

I then added pll_ajax_backend=1 only to Elementor’s elementor_ajax requests using a small jQuery.ajaxPrefilter.

After adding this parameter, the Elementor editor immediately started loading the same controls correctly in the WordPress user locale (ru_RU):

• Тип
• Ярлык
• Текстовая область
• Выпадающий список

The workaround is reproducible and currently resolves the issue.

No page content, Elementor template data, Polylang language assignments, WordPress Site Language, or database records were changed.

This appears to indicate that Elementor editor AJAX requests are not being recognized by Polylang as backend/admin AJAX requests, causing Polylang to initialize them in the site/content locale (de_DE) instead of the WordPress user locale (ru_RU).

Could you please confirm:

1. Is pll_ajax_backend=1 expected for this type of admin/editor AJAX request?
2. Should Polylang automatically recognize these Elementor AJAX requests as backend requests?
3. Is this something that should be fixed on the Polylang side, or should Elementor explicitly provide this backend marker/context?

I have also sent the HAR capture, before/after screenshots, and the working workaround to Elementor Support so that both sides can investigate the interaction.

Thank you.