Warning: Undefined array key after update to 3.25.0

Hi there,

Thank you for contacting us.

Please try to roll back to version 3.24.7; this should resolve this issue. To accomplish this, you can use our rollback feature –?https://elementor.com/help/rolling-back-to-a-previous-version-of-elementor/

Hope this will help to resolve your issue.

Kind regards,

• This reply was modified 3 weeks, 6 days ago by Milos.

Thanks for the reply. Yes. I did a version rollback right away. But I’m more interested in whether the problem will be fixed in the next updates so I can use the current version of Elementor?

Hi there,

Thanks for contacting us again.

I am not able to provide you with ETA of the resolution of this issue, but once the fix is released, you will receive a notification on your WordPress dashboard informing there is a new update for Elementor plugins and we will update it on our changelog page:

https://elementor.com/pro/changelog/

https://github.com/elementor/elementor#changelog

What I can do from my side is vote for this issue in our internal bug report system so that it receives higher priority and hopefully gets fixed in one of the next plugin updates.

We apologize for this inconvenience and appreciate your patience while we work on this problem.

Please let me know if you need further assistance.

Kind Regards,

I found out that this notification disappears if you disable Optimized Control Loading in Elementor > Settings > Experiments and Features menu.

But still I would like to clarify if this problem will be solved in the future.

Hi again,

Thank you for reaching back and for your great feedback,

Our developers are already aware of this issue and are actively working on a solution. Unfortunately, we do not have a specific timeline for resolution, but we are doing our best to address it as soon as possible.

If you have any further questions or need assistance in the meantime, please feel free to reach out.

Best regards

• This reply was modified 1 week, 6 days ago by Milos.

Due to inactivity this ticket has been closed.

The problem seems to have been fixed in version 3.25.9.