• Hello i am receiving this error:

    Warning: Trying to access array offset on value of type bool in /wp-content/plugins/elementor/includes/base/widget-base.phpon line223

    Warning: Undefined array key -1 in wp-content/plugins/elementor/includes/base/controls-stack.phpon line695

    Ive downgrated to 3.12.2 and the error still persists, my elementor version is : 3.25.3

    Elementor version:

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Md. Anower Hossain

    (@anowerhossain16)

    Hi @spyr05,

    Thanks for sharing the report with us. It seems that the error is triggering from the Elementor widget-base.php. We can relate the issue.

    We have already contact Elementor for that. But to ensure the proper implementation, we might need to test the issue in every possible way. Please contact our technical support team for further debugging and resolution.
    Here is the contact link: https://happyaddons.com/contact-us/
    Thanks and have a nice day.


    I have the same problem. When updating Elementor and Elementor Pro to the latest version my website stops working correctly

    Ricardo

    (@ricardotjs)

    @anowerhossain16, This error happens only when “Text Stroke” is enabled.
    I hope I have helped your team.

    Plugin Support Md. Anower Hossain

    (@anowerhossain16)

    Hi @sibrinca, @ricardotjs,

    Thanks for your reaching out to us and sharing your concern and findings. We are aware about the issue and investigating now.
    I will get back to you with the possible guidance and update soon.
    Thanks for your cooperation.
    Have a nice day.

    In my case everything works again if I disable the “Happy Tooltip” function.

    Thread Starter spyr05

    (@spyr05)

    Ive received this solution from happy addons support and it worked for me:

    One thing you can check is that, Goto your?Admin Dashboard > Elementor > Settings > Features?section. and check the status of the “Element Caching” option. If Element Caching is enabled, disable it. If disabled, Enable it.?It might solve the issue.?

    In my cause it was set on default so i enabled it and the error was gone

    The reported issue has been fixed in version 3.13.0.

    Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.