Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter zsimunovic

    (@zsimunovic)

    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.

    Thread Starter zsimunovic

    (@zsimunovic)

    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.

    Thread Starter zsimunovic

    (@zsimunovic)

    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.

    Thread Starter zsimunovic

    (@zsimunovic)

    Hi Annie,
    I updated SiteOrigin widgets bundle 1.9.5
    After activation, Elementor 1.5.5 still doesn’t work.
    Zeljko

    Elementor SysInfo:
    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.5 – 2:1504
    2017-07-27 05:59 +00:00

    Thread Starter zsimunovic

    (@zsimunovic)

    Hi alexgso,
    of course, I do not claim that my statement is correct in 100% of cases, I am speaking from my experience and from my environment.

    Related to GitHub:
    I remember visiting GitHub, but I do not remember the issue I posted there.
    I do not even remember that I opened the account there.
    I visited GitHub but could not find my post.
    Please send it to me.
    I do not understand your statement that you cannot replicate the issue.

    Thread Starter zsimunovic

    (@zsimunovic)

    epanuelos (@epanuelos)

    Very simple.
    The combination of SiteOrigin Widgets Bundle and Elementor doesn’t work.
    If you want to use Elementor, you must deactivate SiteOrigin Widgets Bundle.
    If you want to use SiteOrigin Widgets Bundle, you will not be able to use Elementor.
    Until the Elementor or SiteOrigin Widgets Bundle update, when this combination will work.

    Thread Starter zsimunovic

    (@zsimunovic)

    Of course, I intend to use the cache:) I just left it turned off for the moment, at this stage of developing the website and experimenting with plugins.
    I completely deleted the plugin, but the login problem is still present.
    I agree with your statement that the problem might be at the server level. I’ll check with my hosting provider. Thank you very much for your support.

    Thread Starter zsimunovic

    (@zsimunovic)

    Ever since I have installed WP Super Cache plugin and activated it for the first time, I have not turned the cache on, it is permanently turned off.
    Even in the WP Super Cache settings, I started deleting the cache, even though it is turned off, but the login problem is still present.

    Thread Starter zsimunovic

    (@zsimunovic)

    Thank you, James, for your suggestions. I tried everything you suggested, but the problem is still present.
    And despite the deactivation of all plugins and set the Twenty Seventeen theme, I can not login into WP after I close my browser and open it again, without previous deleting the browsing data using the browser tool. In fact, it’s enough to select just erasing “cached images and files” and login into WP it is possible after reopening the browser. Please note that the WP plugin “WP Super Cache” is deactivated and I believe the problem is unrelated to it.
    It is interesting that if I first login into CPanel on the ISP server, and then into WP, the login into WP it is possible after reopening the browser (without previous deletion of the browsing data), with the same procedure (firstly CPanel, then WP).

    Thread Starter zsimunovic

    (@zsimunovic)

    Yes

    Thread Starter zsimunovic

    (@zsimunovic)

    Hi alexgso,
    Here I just temporarily changed the theme to Twenty Seventeen and the problem appears if I activate the SiteOrigin Widgets Bundle. When I turn it off, Elementor does work.
    Also, I’ve deactivated all plugins and left only Elementor and SiteOrigin Widgets Bundle. In this combination, Elementor does not work.

    Thread Starter zsimunovic

    (@zsimunovic)

    Dear Sirs, thank you for participating in this brief discussion and in your suggestions. Fortunately, the problem is solved. With more careful testing of plugins, I found that SiteOrigin Widgets Bundle (ver. 1.9.3) is the cause of the problem. After its deactivation, the Elementor works normally.
    What a pity for SiteOrigin Widgets Bundle since it contains useful plugins. If anyone first finds that compatibility and co-operation between Elementor and SiteOrigin Widgets Bundle have been achieved in the upcoming updates, please let us know. All the best

Viewing 12 replies - 1 through 12 (of 12 total)