Elementor Not Working

  • Resolved zsimunovic

    (@zsimunovic)


    6 years, 9 months ago

    Hi, I am trying to use Elementor in my WP environment – http://www.heris.hr/wp/ – Theme: Appointment(https://webriti.com/appointment/)
    When I open my Test page and start Elementor it tries to load but with no success.
    It seems that the cause of the problem is not the other plugins or the choice of the theme, but the insufficient adaptivity of the Elementor version 1.5.3. (maybe the PRO version does not have this problem). I have deactivated other plugins, returned to the default WordPress theme but Elementor is still not working.
    I would greatly appreciate your help and advice.

    Please see below
    WP Elementor System Info

    == Server Environment ==
    Operating System: Linux
    Software: Apache
    MySQL version: 5.6.36
    PHP Version: 7.1.6
    PHP Max Input Vars: 5000
    PHP Max Post Size: 20M
    GD Installed: Yes
    Elementor Library: Connected

    == WordPress Environment ==
    Version: 4.8
    Site URL: http://www.heris.hr/wp
    Home URL: http://www.heris.hr/wp
    WP Multisite: No
    Max Upload Size: 20 MB
    Memory limit: 64M
    Permalink Structure: /%category%/%postname%/
    Language: hr
    Timezone: 1
    Debug Mode: Active

    == Theme ==
    Name: Appointment
    Version: 2.6.4
    Author: Webriti
    Child Theme: No

    == User ==
    Role: administrator
    WP Profile lang: hr
    User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

    == Active Plugins ==
    Contact Form 7
    Version: 4.8
    Author: Takayuki Miyoshi

    Elementor
    Version: 1.5.3
    Author: Elementor.com

    Jetpack by WordPress.com
    Version: 5.1
    Author: Automattic

    Limit Login Attempts
    Version: 1.7.1
    Author: Johan Eenfeldt

    Page Builder by SiteOrigin
    Version: 2.5.8
    Author: SiteOrigin

    SiteOrigin CSS
    Version: 1.1.4
    Author: SiteOrigin

    SiteOrigin Widgets Bundle
    Version: 1.9.3
    Author: SiteOrigin

    WP Super Cache
    Version: 1.4.9
    Author: Automattic

    == Debug ==
    Errors:
    TypeError: elementorFrontend.getScopeWindow(…).jQuery is not a function
    at http://www.heris.hr/wp/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=1.5.3 – 2:1504
    2017-07-12 18:16 +00:00
    x 13 times

    (ZS) My insertion – Inspect the Test page – while trying to edit (open) the Test page with the Elementor
    Uncaught TypeError: elementorFrontend.getScopeWindow(…).jQuery is not a function
    at g (frontend.min.js:2)
    at d.initHandlers (frontend.min.js:2)
    at n.initFrontend (editor.min.js:3)
    at n.onPreviewLoaded (editor.min.js:3)
    at HTMLIFrameElement.dispatch (jquery.js:3)
    at HTMLIFrameElement.r.handle (jquery.js:3)

Viewing 7 replies - 16 through 22 (of 22 total)
1 2
  • alexgso

    (@alexgso)

    6 years, 9 months ago

    Hi zsimunovic,

    logologics’s explanation of what I meant is correct.

    With that said, our lead developer has managed to replicate this issue. Do you have the contact form enabled? If so, does it work if you temporarily disable it? You can see which widgets are active by navigating to WP Admin > Plugins > SiteOrigin Widgets – you can also deactivate widgets on this page.

    I ask as that was the cause for him, although admittedly, I’m able to have the contact form enabled and added to a page via Elementor without issue so his cause may be something different.

    Regarding GitHub, sorry about that – I had confused you with someone else. They created an issue here.

    Thread Starter zsimunovic

    (@zsimunovic)

    6 years, 8 months ago

    Hi LogoLogics & alexgso,

    I finally found the cause why Elementor could not work when SiteOrigin Widgets Bundle was activated.

    After consultation with my host provider, the following is identified:
    In the Google Chrome Developers console under Sources, there has been encountered an error in previewing, when a post is edited by the Elementor plugin.

    <b>Fatal error</b>: Uncaught Error: Cannot unset string offsets in
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/widgets/button/button.php:362
    Stack trace:
    #0
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(164):
    SiteOrigin_Widget_Button_Widget->modify_instance(‘A’)
    #1
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(360):
    SiteOrigin_Widget->widget(Array, ”)
    #2
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/widgets/cta/tpl/default.php(10):
    SiteOrigin_Widget->sub_widget(‘SiteOrigin_Widg…’, Array, ”)
    #3
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(211):
    include(‘/home/heris/pub…’)
    #4
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/compat/elementor/elementor.php(54):
    SiteOrigin_Widget->widget(Array, Array)
    #5 /home/heris/public_html/wp/wp-includes/class-wp-hook.php(298):
    SiteOrigin_Widgets_Bundle_Elementor->enqueue_preview_script in <b>/home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/widgets/button/button.php</b>
    on line <b>362</b><br />

    There was modified the file:
    /home/heris/public_html/wp/wp-content/plugins/so-widgets-bundle/widgets/button/button.php

    which is identified in the Google Chrome Developers console and caused errors in the work of Elementor.

    Certain lines were put under comments, and in the SiteOrigin Widgets Bundle plugin, there has been turned the Button widget off, to not call functions.

    What is all excluded or placed under a comment:
    //unset($instance[‘icon_selected’]);
    //unset($instance[‘icon_color’]);
    //unset($instance[‘icon’]);

    //unset($instance[‘align’]);
    //unset($instance[‘theme’]);
    //unset($instance[‘button_color’]);
    //unset($instance[‘text_color’]);
    //unset($instance[‘hover’]);
    //unset($instance[‘font_size’]);
    //unset($instance[’rounding’]);
    //unset($instance[‘padding’]);

    //unset($instance[‘id’]);

    Now Elementor and most of the SiteOrigin widgets work.

    Thank you very much for your support.

    alexgso

    (@alexgso)

    6 years, 8 months ago

    Hi zsimunovic,

    That’s odd. I can’t seem to replicate that issue. Can you please try reverting wp-content/plugins/so-widgets-bundle/widgets/button/button.php and changing:

    		if( empty($instance['attributes']) ) {
			$instance['attributes'] = array();
			if(isset($instance['id'])) $instance['attributes']['id'] = $instance['id'];
			unset($instance['id']);
		}

    To:

    		if( empty( $instance['attributes'] ) ) {
			$instance['attributes'] = array();
			if( isset( $instance['id'] ) ) {
				$instance['attributes']['id'] = $instance['id'];
				unset($instance['id']);
			}
		}

    Does that help?

    Thread Starter zsimunovic

    (@zsimunovic)

    6 years, 8 months ago

    Hi LogoLogics & alexgso,
    First, my apology for the delay, but I was occupied with other jobs.
    I’ve implemented your code Alex, and the SO Widgets Bundle – Button widget problem is no longer present.

    In a mean time, I contacted people from Elementor and pointed them to the problem.
    In their latest version 1.6.2, they have solved the problem so that the Elementor does not get stuck when it comes to a code error, but it is loaded to the end and continues to work.

    But, this is still not the case with the code error described in the button.php. In this case, the Elementor is not fully loaded but now displays a warning window and instructions for removing the error.
    But in my case, the button.php error has been solved by the described implemented code, for now. SiteOrigin must implement the code in their widget.

    Currently, I’ve made the following updates:
    WordPress 4.8.1
    Elementor 1.6.2
    Jetpack 5.2.1
    SO Page Builder 2.5.10
    SO Widgets Bundle 1.9.6

    Although there are some errors detected by the Google Chrome Developers console, for example:
    1) JetPack gallery-settings.js
    2) SiteOrigin Page Builder siteorigin-panels-259.min.js:2
    3) JetPack /wp/wp-content/plugins/jetpack/css/%22https:/fonts.googleapis.com/css?family=Open+Sans%22

    the Elementor is get loaded normally and continue to work.

    LogoLogics

    (@logologics)

    6 years, 8 months ago

    Hi,

    I am not sure what both developers of Elementor and Pagebuilder SiteOrigin have to say about this, but I notice you, not only use the SiteOrigin widget bundle, but also keep the SiteOrigin pagebuilder active + the Elementor pagebuilder?

    I tested this myself ( not extensively though ) and that combo seemed to play nice together ). However, I think it is never a good idea to use two different pagebuilders in the same site? Are you still having these errors if you deactivate the SIteOrigin Pagebuilder I wonder?

    Annie

    Thread Starter zsimunovic

    (@zsimunovic)

    6 years, 8 months ago

    Hi LogoLogics,
    I’ve just made the Elementor 1.6.3 update.

    When I deactivate the SO Pagebuilder the error
    2) SiteOrigin Page Builder siteorigin-panels-259.min.js:2
    disappears.

    LogoLogics

    (@logologics)

    6 years, 8 months ago

    Right, so you should decide which pagebuilder to use and recreate the content in only that pagebuilder. Two different pagebuilders is usely an accident waiting to happen!:-)
    It’s like two captains running the same ship!

    Annie

    • This reply was modified 6 years, 8 months ago by LogoLogics.
Viewing 7 replies - 16 through 22 (of 22 total)
1 2
  • The topic ‘Elementor Not Working’ is closed to new replies.