Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔃 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined (PR #27353) - [ED-14910] #19345

Open
5 tasks done
HeavyLogic opened this issue Aug 3, 2022 · 37 comments · May be fixed by #27353
Open
5 tasks done
Labels
bug Indicates a bug with one or multiple components. component/code Indicates when a topic is related to a component’s code. document/settings References a Document's (Posts, Pages, Templates, Popups, etc.) settings. editor/site-settings References any component related to the Editor Site Settings. status/has-pr Indicates that an Issue, or Discussion has a companion Pull Request awaiting to be merged.

Comments

@HeavyLogic
Copy link

HeavyLogic commented Aug 3, 2022

Prerequisites

  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
  • The issue still exists against the latest stable version of Elementor.

Description

When I press "edit with Elementor", there's like 30% chance that this error in console will pop up and Elementor stops loading:
Uncaught TypeError: elementor.settings.page is undefined

I think this happens only in Firefox.
//add: Client says he gets same issue in Chrome, but I can't reproduce it. It's easier to catch this bug in Firefox.

Steps to reproduce

I did everything from scratch to test this:

  1. Install new Wordpress 6.0.1
  2. Install new Elementor 3.6.8
  3. Install new Hello Elementor 2.6.1
  4. Disable all extensions in Firefox
  5. Create new page
  6. Press "Edit with Elementor" with closed Dev Tools
  7. Elementor can load at this moment. If it is:
  8. Go back in browser, press F5 with closed Dev Tools
  9. Repeat from step 6 till Elementor stops loading
  10. Open Dev Tools and check error in console

This error doesn't appear with opened Dev Tools. Probably because it disables cache while it's open.

Isolating the problem

  • This bug happens with only Elementor plugin active (and Elementor Pro).
  • This bug happens with a Blank WordPress theme active (Hello theme).
  • I can reproduce this bug consistently using the steps above.

System Info

system-info-elem-test2-03-08-2022.txt

@HeavyLogic HeavyLogic added the bug Indicates a bug with one or multiple components. label Aug 3, 2022
@HeavyLogic HeavyLogic changed the title 🐞 Bug report: 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined Aug 3, 2022
@rami-elementor rami-elementor added the editor/site-settings References any component related to the Editor Site Settings. label Aug 6, 2022
@rdarcy1
Copy link

rdarcy1 commented Aug 17, 2022

I have this bug as well, worth noting it doesn't seem to be affected by activating Elementor safe mode.

@Joni-L
Copy link

Joni-L commented Aug 24, 2022

Possible workaround seems to be to do a reload while having the console open and the "disable cache" option selected in the network pane.

Also always happens first time editing a newly published post.

@pryley
Copy link

pryley commented Aug 25, 2022

Here is a screen recording of the bug in action:

CleanShot.2022-08-25.mp4

@pryley
Copy link

pryley commented Sep 4, 2022

@lorre851
Copy link

lorre851 commented Oct 14, 2022

Bump.

I have the exact same issue since the last update. Extremely annoying and crippling productivity! Disabled all plugins to no avail.

Installed plugins:

  • CookieYes | GDPR Cookie Consent v3.0.3
  • Duplicate Page v4.4.9
  • Elementor v3.7.8
  • Elementor Pro v3.7.7
  • Image optimization service by Optimole v3.4.5
  • Rank Math SEO v1.0.99
  • TC Custom JavaScript v1.2.3
  • Unlimited Elements for Elementor v1.5.32
  • Wordfence Security v7.7.1

PHP version 8.1
FireFox version 105.0.3
WordPress version 6.0.2

JS stack trace:
Uncaught TypeError: elementor.settings.page is undefined isScrollSnapActive https://domain.be/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.7.8:2 getDefaultSettings https://domain.be/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.7.8:2 e https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 initSettings https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 init https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 Module https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 child https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 child https://domain.be/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.7.8:2 initOnReadyComponents https://domain.be/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.7.8:2 init https://domain.be/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.7.8:2 initFrontend https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 onPreviewLoaded https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 onPreviewLoaded https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 Backbone 9 initPreview https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 onStart https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 onStart https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 Backbone 3 <anonymous> https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 <anonymous> https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3 <anonymous> https://domain.be/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.8:3

EDIT: it looks like this problem is Firefox - only. Chrome works fine.

EDIT 2: experienced this too on a new WordPress 6.1 installation with no plugins installed but Elementor + Elementor Pro, 3.8.0, again on Firefox.

@bkno
Copy link

bkno commented Nov 5, 2022

I have this too.

Can confirm Joni-L's workaround works for now. Not so good for clients but I was just glad to be able to make edits again myself!

@Pumpk1in
Copy link

I can confirm this bug on my end. Only Firefox.
Never had this problem until I tried to use Firefox a couple of days ago. (was always using Vivaldi...)

Firefox or Elementor bug, don't know but it is annoying as hell and needs to be fixed. 😬

@grex22
Copy link

grex22 commented Mar 3, 2023

Same here, Firefox only - Able to reproduce using same above steps

@Tiiara
Copy link

Tiiara commented Mar 20, 2023

Same here, Firefox only. Chrome and Edge work fine.

@cadeyrn
Copy link

cadeyrn commented Mar 20, 2023

Same here.

@gravitytechau
Copy link

+1

Confirming the annoying bug in Firefox.

@NichCrusie
Copy link

Just adding in that this bug is still present and only in Firefox.

As mentioned by @Joni-L that a possible work around (which works for me) is to open dev tools > network > disable cache > reload.

@BackuPs
Copy link

BackuPs commented May 4, 2023

Same issue here. Even if you install p[lugins like elementKit Lite the button they add into the editor is missing. It looks like its a firefox related issue. It does not matter what language version of firefox i use. The problem always occurs.

@HeavyLogic
Copy link
Author

I'm not getting this error anymore on Elementor 3.12.2.

@BackuPs
Copy link

BackuPs commented May 5, 2023

@HeavyLogic I got it since 3.12.2. In a complete new wordpress install. Older installs i do not get it in the same firefox.

@callumjohnspiller
Copy link

this is still happening for me, in firefox

@rykiniax
Copy link

Same problem here, I got crazy trying to find out how to fix it.

@callumjohnspiller
Copy link

@rykiniax The workaround by @Joni-L is good. If you have the network tab open and cache disabled, a couple of refreshes of the page seems to do the job.

@suzieq-1
Copy link

Hi, this is still happening. Please fix this asap, not worth getting the Pro version if you can't reliably use it on Firefox.
Firefox version: 117 en Elementor 3.16.0

@gravitytechau
Copy link

Agree with @suzieq-1 - having this issue for a year is a bit too much.

I was testing Elementor to see if I should go with that or Divi, and this was the thing that sent me to Divi.

@rloes
Copy link

rloes commented Sep 25, 2023

I only got this error very recently, on a new pc using Firefox. I get it on multiple sites now and almost every time I try to go into the editor.

I usually need a couple of refreshes.

Please fix!

@makifaykan
Copy link

I continue to experience this problem. There must be a solution to this.

@wpwebbouw
Copy link

Possible workaround seems to be to do a reload while having the console open and the "disable cache" option selected in the network pane.

Also always happens first time editing a newly published post.

Thanks a lot for this workaround Joni-L. I've been looking for solutions for quite a while, but Elementor support nor Mozilla support seem to be aware of it. I can confirm it happens in Firefox and nog in other browsers. Glad I can use Elementor now in my favorite browser.

@BackuPs
Copy link

BackuPs commented Nov 23, 2023

I continue to experience this problem. There must be a solution to this.

More then a year and not a single reply from elementor support?

@gravitytechau
Copy link

More then a year and not a single reply from elementor support?

If there's no compelling reason to use Elementor, perhaps you should investigate Divi? They have a Black Friday sale on for the lifetime (pay once) license for $187USD. https://www.elegantthemes.com/join/lifetime/?sale=black-friday-2023#pricing-table-top

@mbaierl
Copy link

mbaierl commented Dec 5, 2023

Same here... let's write the support as well.

@janisdonis2
Copy link

The same on Chrome, even on standard theme and elementor.

@janisdonis2
Copy link

Update: Moved the site to a new app on the same server, with the same configuration, with Duplicator plugin and now Elementor works fine and all site works normally. Strange.

@mbaierl
Copy link

mbaierl commented Dec 13, 2023

Elementor is pretty unusable in Firefox. Happens on every 2nd load of the editor, on all of my sites...

@mbaierl
Copy link

mbaierl commented Jan 31, 2024

Still the same with Elementor 3.19. Unusable in Firefox, as the Editor does not load.
The "support" simply says "use Chrome", which is not always a valid option.

Please fix this @avivu

@momo-fr
Copy link

momo-fr commented Jan 31, 2024

Yeap, if using Grid container for me, editor not open -> safe mode.

@mbaierl
Copy link

mbaierl commented Feb 12, 2024

Same with Elementor 3.19.1 and 3.19.2.
Elementor is not usable with Firefox, which is a shame @avivu

@momo-fr
Copy link

momo-fr commented Feb 19, 2024

Same for me, in some cases the editor does not load. Elementor is very unstable now…

@walent021
Copy link

Still experiencing this issue - Firefox 122.0.1, Wordpress 6.4.3, Elementor 3.19.2
Same steps as above

@momo-fr
Copy link

momo-fr commented Feb 21, 2024

I also notice a slowdown in the editor if I use the Grid container (with Firefox Mac).

@Ngenaudet
Copy link

On my side I find out the issue. There was too many ajax request on background.

Here my debug process :

  • activate wp_debug in the wp_config file ( wp_debug, log and display)
  • activate the debug mode on elementor
  • see the return of admin-ajax

https://forum.infinityfree.com/docs?topic=49336

image

@m1ga
Copy link

m1ga commented Apr 30, 2024

Same here with latest 3.21.4

Error is in:

const scrollSnapStatus = elementorFrontend.isEditMode() ? elementor.settings.page.model.attributes?.scroll_snap : elementorFrontend.config.settings.page?.scroll_snap;

elementor.settings.page is undefined. Please add a check around that and set it to false if not present.

@nicholaszein nicholaszein changed the title 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined 🔃 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined (PR #27353) May 21, 2024
@nicholaszein nicholaszein added status/has-pr Indicates that an Issue, or Discussion has a companion Pull Request awaiting to be merged. component/code Indicates when a topic is related to a component’s code. labels May 21, 2024
@nicholaszein nicholaszein changed the title 🔃 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined (PR #27353) 🔃 🐞 Bug report: Uncaught TypeError: elementor.settings.page is undefined (PR #27353) - [ED-14910] May 22, 2024
@nicholaszein nicholaszein added the document/settings References a Document's (Posts, Pages, Templates, Popups, etc.) settings. label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates a bug with one or multiple components. component/code Indicates when a topic is related to a component’s code. document/settings References a Document's (Posts, Pages, Templates, Popups, etc.) settings. editor/site-settings References any component related to the Editor Site Settings. status/has-pr Indicates that an Issue, or Discussion has a companion Pull Request awaiting to be merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.