Hi @pozoalcon
Thank you for contacting Elementor Support. Can you please check your error logs and provide the stack trace of the critical error you see?
Kind regards,
If this is not your topic and if you need support then per the forum guidelines please start your own topic.
https://ww.wp.xz.cn/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
You can do so here.
https://ww.wp.xz.cn/support/plugin/elementor/
The other replies have been archived. Start your own topics instead.
Please do not post large code or responses like that here, it doesn’t work after ~10 lines or so.
If you need share that data please use https://gist.github.com/ or https://pastebin.com/ or the like instead and post the link to that paste.
Pasting that data in a reply just makes an unreadable mess.
I don’t understand this answer. I posted the error log because elementor support asked me to. I also don’t understand why you have archived the other answers. And I also don’t understand why it refers me to this page https://ww.wp.xz.cn/support/plugin/elementor/ to create my themes, when that is what I have done. Please repost the other answers because it is necessary to solve an important problem. With this attitude you are hindering the work of many people.
-
This reply was modified 1 year, 5 months ago by
pozoalcon.
@pozoalcon this moderation was done by WordPress Moderation team and not the Elementor team. I guess the error logs need to be pasted elsewhere and then embedded here.
-
This reply was modified 1 year, 5 months ago by
contemplate.
Perhaps to help fix your problem, I can shed some light on how to solve it.
You have to go to Elementor > Settings > Features and disable element caching, it is enabled by default.
After this, everything works as it should.
yesterday indeed elementor issued a new feature whose name if I’m not mistaken is element caching and it’s still in the beta stage, and that’s also what might create problems in this Elementor 3.26.0 update.
Hi,
In my case it was due to a compatibility problem between the The7 theme and Elementor 3.26.
With the v.12.2.0 update of the theme it has been resolved
Thanks mudzhaqjs, but in my case the problem persists despite disabling the elements cache.
Hi, @jsalainfordisa. That URL is incorrect. Isn’t it?
ups, sorry 😉
the correct URL is https://elementor.com/pro/changelog/
3.26.1 – 2024-12-17
Fix: Restore deprecated Plugin::enqueue_styles() function to avoid errors with 3rd party plugins
Thank you @jsalainfordisa .
Ok, let’s see if they update the free version too.
Version 3.26.2 still gives the same problem, as you can see in this image. https://ibb.co/ZMyKvNs
The same thing happened with 3.26.1.
-
This reply was modified 1 year, 5 months ago by pozoalcon.
Hi @pozoalcon
Thank you for sharing the error stack trace. Please note that the plugin triggering this error is the auxin-elements. For reference: https://prnt.sc/V6tcZ9vlhYcs
I see that they have received the following report from one of their users where they provided a workaround for this: https://ww.wp.xz.cn/support/topic/plugin-brealks-the-phlox-theme/
For everyone else experiencing this issue, please check the error stack trace to identify the conflicting plugin and report the issue to their developers. Please note that Elementor 3.26 version removed the deprecated Scheme method. This was communicated to third-party developers and it is a part of our Developer release notes: https://developers.elementor.com/elementor-3-26-developers-update/
Kind regards,
Hi @nemanjat .
I followed the instructions you gave me and the problem has been resolved. Thank you very much.
Best regards.
