CoolHappy

Thank you for the detailed video recording.

I was able to reproduce the issue on my end.
What happened is that previously the child_of condition was not being considered as a post type, and the template rendering logic was using the sub_name value instead of the sub_id.
We recently updated the logic to render the template and evaluate conditions based on the sub_id rather than the sub_name, which resolved the original issue but also introduced this behavior with translated child pages.

Could you please apply the following one-line code change and test again?
File:connect-polylang-elementor/includes/connect-plugins.php
Under the function condition_sub_id_translation() (around line 450), replace:

if ( in_array( $parsed_condition[‘sub_name’], get_post_types(), true ) ) {

with:

if ( get_post_type( $sub_id ) ) {

You can refer to this screenshot for guidance:
https://prnt.sc/KHhzbQetvj9k
After making this change, please check whether everything is working as expected. If you continue to experience any issues or find anything else unusual, feel free to get back to us and we’ll be happy to assist further.

Thank you for your cooperation and testing.

Thanks for the update.
I have fixed the issue and created a pull request. The solution will be available upcoming update.

• This reply was modified 1 week, 4 days ago by CoolHappy.

Thank you for the detailed explanation.
From your description, it appears that the issue is related specifically to the mobile menu setup rather than the translated header itself.
On our end, we tested the same scenario using:

• one header for both desktop and mobile in the default language,
• translated versions of that header for each language,
• and the display condition set to “Entire Site” only for the default language header (no additional condition was needed for the translated headers).

In our tests, the translated headers were rendering correctly on both desktop and mobile according to the current page language.
In your case, the issue may be caused by:

• overlapping display conditions,
• cached menu rendering,
• or a conflict with another plugin/theme component.

Regarding the critical error:
4.0.4.2 is an invalid version
this appears to be related to the Elementor PRO / PRO Elements plugin version handling and could potentially affect Elementor behavior as well.
As a first step, could you please verify whether the issue still occurs when using:

• an older/stable version of Elementor and Elementor PRO / PRO Elements,
• or temporarily disabling Elementor PRO / PRO Elements to rule out a compatibility conflict?

To help us reproduce the exact setup and investigate further, could you also share:

• a short screen recording of the issue,
• the exact header structure/setup,
• the display conditions configured for each header,
• and a list of active plugins along with their versions?

At the moment, we are unable to reproduce the issue on our end, as the translated headers are rendering correctly on both desktop and mobile screens based on the selected language.
Looking forward to your update.

Hi @elemeskutya ,
Could you please share the following details so we can properly investigate the issue?

• Plugin versions
• Elementor / Elementor Pro versions
• Screenshots of the issue
• Browser console errors (if any)
• Reproduction scenario

This information will help us reproduce the issue on our end and identify the exact conflict related to Loop Grid / Loop Item templates.

@carlosmayor Please ignore last response.

Hi,
Thank you for reporting this issue.
The warning you’re seeing: Undefined array key ‘elementor_preview’ is caused by the plugin accessing the elementor_preview value from the URL without properly ensuring the key exists first. In PHP 8+, accessing a non-existent array key triggers a warning, which is why your error logs are filling up with thousands of entries.
To resolve this, please update the following file:
File path:
/connect-polylang-elementor/includes/elementor-assets.php
(around line 57)
Replace this line:

$is_preview = isset( $_GET[‘elementor_preview’] ) && ! empty( sanitize_key( wp_unslash( $_GET[‘elementor_preview’] ) ) );

With the following code:

$preview_val = isset( $_GET[‘elementor_preview’] ) ? sanitize_key( wp_unslash( $_GET[‘elementor_preview’] ) ) : ”; $is_preview = $preview_val !== ”;

This change ensures that $_GET['elementor_preview'] is only accessed when it actually exists, preventing PHP 8 from generating the “Undefined array key” warning. There is no change in functionality — this is strictly a compatibility fix and will stop the excessive log entries.
Please refer to the screenshot here for reference:
https://prnt.sc/HSTOcEUF9HzX
After applying this change, the warnings should stop immediately.
We will include these changes in upcoming updates.
Let us know if you need any assistance.