Open askwpgirl opened 2 weeks ago
duplicate of https://github.com/elementor/elementor/issues/24492
but yes: should be fixed as it's not good to have errors in the frontend.min.js
Thanks @m1ga - I searched for this and couldn't find it. It's been give months, so yes, perhaps should be fixed. However, that original ticket is incorrect. This happens on every Elementor edit page regardless of whether the Style Guide is active. It is the Edit page that throws this error, not the Style Guide.
I think when the other issue was posted you still had the "global styleguide" feature in the settings and could turn it off. Now that is not there anymore and you can only change it in the site settings of the editor but it doesn't switch it off completely like before. Nevertheless it shouldn't be there :smile:
definitely an issue in subsequent versions of 3.21.x -- I have rolled back to 3.21.0 for both Elementor and Elementor Pro and the issue does not occur - all pages/templates and posts load in the editor if you upgrade - and throw the Uncaught Exception. I'll be staying at 3.21.0 until there's a fix.
Out of curiosity @stephroseg : does it break something for you in the Editor? I do see that error but the editor works fine. The only error that is causing it not to open is https://github.com/elementor/elementor/issues/19345#issuecomment-2085235911 (you have to open the devtools and reload so it will open)
Both issue should be fixed immediately as "opening the Editor" should be daily business and not produces any error!
Out of curiosity @stephroseg : does it break something for you in the Editor? I do see that error but the editor works fine. The only error that is causing it not to open is #19345 (comment) (you have to open the devtools and reload so it will open)
Both issue should be fixed immediately as "opening the Editor" should be daily business and not produces any error!
Hi @m1ga
This appears to be causing an issue for me, I can't select or use the Manual Post Selection functionality with Unlimited Elements - though everything else seems to work.
I can't be 100% sure, but this seems to be the only new error being thrown
I noticed this error today, as I was editing a page and bought a license for Essential Addons For Elementor. Adding their posts element, shows the layout completely broken and on console log it's the same thing.
frontend.min.js?ver=3.21.5:2 Uncaught TypeError: e.O is not a function
at frontend.min.js?ver=3.21.5:2:39876
at webpackJsonpCallback (styleguide-app-initi…?ver=3.21.5:3:13486)
at webpackJsonpCallback (webpack.runtime.min.js?ver=3.21.5:2:4680)
at frontend.min.js?ver=3.21.5:2:74
@peixotorms - I think your issue with Essential Addons is independent of this error since this error occurs without Essential Addons installed. It might be, like most people, you only noticed because you happened to look at the Console tab due to having issues with something else.
@peixotorms - I think your issue with Essential Addons is independent of this error since this error occurs without Essential Addons installed. It might be, like most people, you only noticed because you happened to look at the Console tab due to having issues with something else.
That would be correct. It was the only issue in the console log.
Essential Addons eventually worked, by downgrading elementor all the way down to 3.20 and back again to the latest version. However, the error is still there for several versions, and it's not great to have these errors, when a simple check to see if it's available could solve it.
ex:
if (e && typeof e.O === 'function') {
// Safely call the function since we've confirmed it's a function
} else {
console.error('e.O is not a function');
}
Anyway, not critical.
Thanks!
You have to think that "using the editor without errors" would be a high priority because if you can't open it you can't use it :shrug:
But most PRs at the moment are about the new Conversion Center
(i know, different teams and so on):
A powerful feature to enhance your online presence. With the ability to create compelling Link in bio pages and easily accessible contact buttons, the Conversion Center is tailored to significantly boost your conversions.
But is there not one Elementor dev that is using Elementor and sees those errors and wants to get rid of them?
Echoing what many others have experienced already ~ the error seems to be present in all current 3.2x.x versions (3.20.0 and 3.21.0 included) even with a vanilla theme and all other plugins disabled. Only downgrading to 3.19.4 + disabling the Global Style Guide has fixed it on my end thus far.
Settings -> Features -> Stable Features -> Global Style Guide --- select "Inactive"
Not ideal from a security or compatibility perspective. Hopefully it gets resolved soon!
thumbs up for @michaelhaberle . same here on all our websites with elementor 3.2.x.x (incl. PRO) and Hello Elementor 3.0.1. only way to get around is to rollback and deactivate the global style guide. it throughs not only this error in console, it prevents the elementor editor to get into saved status after saving. means that it still saved the updated content, but don't let the browser know about this. for the browser (chrome) the pages remains unsaved... which is really annoying as it throughs a nasty leaving alert on autosave or leaving the editor page.
Prerequisites
Description
The Elementor Editor shows the following error on all sites:
Uncaught TypeError: e.O is not a function at frontend.min.js?fsum=fe720b41891a:2:39876 at webpackJsonpCallback (styleguide-app-initiator.min.js?fsum=c3f449f87f77:3:13486) at webpackJsonpCallback (webpack.runtime.min.js?fsum=d3c859a3d439:2:4680) at frontend.min.js?fsum=fe720b41891a:2:74
Steps to reproduce
Expected behavior
No Javascript errors.
Isolating the problem
Elementor System Info
Agreement