• Resolved dzulfriday

    (@dzulfriday)


    Elementor is a great plugin, but it always give conflict problems. One day is OK, next day when you try to edit the same page, suddenly you can’t. This is really stressful.

    Previously, i want to use Storefront theme, but on Storefront theme, Elementor is not friendly at all, image component cannot center align the image, and many other problems. So ok, i switch to other theme, OceanWP. This theme is really working like I want, and can replace Storefront. Yesterday, I completed my work, saved it. And today when I want to edit the page again, Elementor gives me this error:

    Uncaught ReferenceError: butterbean is not defined
        at post.php?post=913&action=elementor:5958

    together with this famous marionette backbone error that I will get no matter what theme i use:

    Uncaught ReferenceError: view is not defined
        at eval (eval at m.template (load-scripts.php?c=0&load[]=underscore,jquery-core,jquery-migrate,backbone,shortcode,utils,wp-util,wp-backbone,media-models,plupload,wp-plupload,jquery-ui-c&load[]=ore,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,mediaelement,wp-mediaelement,media-views,media-editor,media-audiovideo&ver=4.8.2:5), <anonymous>:12:12)
        at c (load-scripts.php?c=0&load[]=underscore,jquery-core,jquery-migrate,backbone,shortcode,utils,wp-util,wp-backbone,media-models,plupload,wp-plupload,jquery-ui-c&load[]=ore,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,mediaelement,wp-mediaelement,media-views,media-editor,media-audiovideo&ver=4.8.2:5)
        at Object.render (backbone.marionette.min.js:sourcemap:22)
        at n._renderTemplate (backbone.marionette.min.js:sourcemap:23)
        at n.render (backbone.marionette.min.js:sourcemap:23)
        at n.render (editor.min.js:2)
        at n.render (load-scripts.php?c=0&load[]=underscore,jquery-core,jquery-migrate,backbone,shortcode,utils,wp-util,wp-backbone,media-models,plupload,wp-plupload,jquery-ui-c&load[]=ore,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,mediaelement,wp-mediaelement,media-views,media-editor,media-audiovideo&ver=4.8.2:5)
        at n.renderChildView (backbone.marionette.min.js:sourcemap:22)
        at n._addChildView (backbone.marionette.min.js:sourcemap:22)
        at n.addChild (backbone.marionette.min.js:sourcemap:22)

    Omg..now what????? OceanWP said this is totally Elementor problem, not them.

    • This topic was modified 7 years ago by dzulfriday.
    • This topic was modified 7 years ago by dzulfriday.
Viewing 11 replies - 1 through 11 (of 11 total)
  • pixelmm

    (@pixelmm)

    i’ve the same problem using oceanWP latest version with latest Elementor version

    Try to update all plugins and switch to another theme and see if it helps.

    Same issue here. Switched to Twenty SeventeenVersion: 1.4 Theme and the error remains.

    [Later edit]
    It doesn’t seem to related to the theme. I’ve bounced back and forth between older versions of Elementor too and the issue remained.

    At least exports work so I can use the template on another WP instance.

    • This reply was modified 6 years, 10 months ago by Push Monkey.

    @benpines

    Whu Is this closed?

    I have the same issue.

    • This reply was modified 6 years, 8 months ago by Luka Petrovic.

    my trial-and-error suggests this is indeed rooted in Elementor, and this work-around seems to work:

    here we go: Tireless experimentation, got me here:

    – Elementor *hangs* with the loading Icon in the body of a page/post when those are not named or published
    – Elementor loads *very promptly* (seconds) When I click on the elementor loading icon *after naming and publishing the page/post! (could be simply clicking in body of page/post)

    Experiment with this and let us know if you can confirm this protocol, or, improve it according to your findings. For my needs, it is offering a work-around that let’s me return to getting work done :-)…………………

    Curious to hear if others have similar results, and especially hoping to hear from Elementor to confirm that they are aware of the issue and perhaps we can help them by experimenting and giving them specific information. It helped me greatly to isolate the issue to Elementor, as I was about to restore my sites to an earlier date when discovering the “workaround” described above.

    Cheers,

    Peter

    The issue is related to some php error in a child theme. Its hard to debug with so unrelated error…

    Thank, Luka! – I am using Page Builder Framework Child Theme, are you suggesting that the “fix” would have to be done by the theme author of my child theme, rather than by the gentle people at Elementor? (I *do* appreciate elementor VERY much, and am definitely patient with resolution to these tricky issues).

    Thanks,
    Peter

    I have the same issue…

    Hi, I have same problem in two websites.

    Hi, now I have same problem in three websites.

    I just cloned a local site and am going through the site to check for errors. I noticed the butterbean console log on some pages. However, it is not doing it on the local site. Using same environment settings on both. Using OceanWP theme with basic OceanWP provided child theme.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Butterbean is not defined? Elementor is not opening’ is closed to new replies.