• Resolved huntersbest

    (@huntersbest)


    We are using SO Widgets on most pages, but 2 pages use Elementor (frontpage and 1 other) for content. On the frontpage updating to 1.58.4 caused a fatal Error in Combination with Elementor 3.19.2 for NOT logged in users.

    Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in ##/wp-includes/blocks.php:

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 22 total)
  • Plugin Support Andrew Misplon

    (@misplon)

    Hi, thanks for getting in touch. I’ve tried to recreate the issue but haven’t been able to do so yet. If you have access to the WP admin you can rollback using https://www.ads-software.com/plugins/wp-rollback/ or you can rollback manually using the ZIP file download option here https://www.ads-software.com/plugins/so-widgets-bundle/advanced/. Perhaps you can export the layout from the page in question, upload it to WeTransfer or any online location and share the link?

    Plugin Contributor alexgso

    (@alexgso)

    Hi Hunter,

    We’ve been able to identify a situation where this can happen, and we’ll be releasing an update shortly that resolves this issue. To avoid this issue in the meantime, I recommend following the advice suggested by Andrew as that’ll allow you to revert to a version that doesn’t have this potential error.

    Kind regards,
    Alex

    Thread Starter huntersbest

    (@huntersbest)

    Ah, thank you very much! We have rolled back the version and are eagery awaiting the update.

    Kind regards

    Plugin Support Andrew Misplon

    (@misplon)

    Thanks for your understanding. Alex has resolved the issue, and an update has been released. Please give it a try and let us know how you get on.

    Thread Starter huntersbest

    (@huntersbest)

    I just updated the plugin https://medlabor.dev.azedo.at/ with no different result. The only idea I got left, is something within the elementor content. Please let me check and get back to you as soon as possible.

    Plugin Contributor alexgso

    (@alexgso)

    Hi Hunter,

    Thanks for trying. I’m having trouble replicating this issue after that the changes made in that release. Can you please send me a copy of your layout? You can do this by opening any page that’s affected by this issue in the editor. Click the 3 vertical dots at the top right of the screen. Select Code Editor and you’ll see the markup for the current page. Copy the markup and paste it on this page. Please reply with a link to the Pastebin.

    Kind regards,
    Alex

    Thread Starter huntersbest

    (@huntersbest)

    I tested the page, but this time by duplicating it and removing block after block. Obviously, someone added a SO Widget into the Elementor Layout. How, I do not know, because I cannot reproduce this. Removing this block (Accordion) from the duplicated page solved the fatal error.
    What I will do now, is finding an equivalent Elementor Block and substitute the SO Widget.

    I will also submit the layout. https://pastebin.com/tjudpce3

    • This reply was modified 9 months, 3 weeks ago by huntersbest.
    Plugin Contributor alexgso

    (@alexgso)

    Hi Hunter,

    Thanks. That appears to be the View Source of the page on the front end rather than the markup in the Block Editor. You can access that by opening that page in the editor. Click the 3 vertical dots at the top right of the screen. Select Code Editor and you’ll see the markup for the current page. Copy the markup and paste it on this page. Please reply with a link to the Pastebin.

    SiteOrigin Widget Bundle widgets can be added using Elementor. It should, in theory, work without issue. I’ll need to run some tests using the layout to work out what’s going on.

    Kind regards,
    Alex

    Thread Starter huntersbest

    (@huntersbest)

    ah sorry! I should not hurry, when reading: https://pastebin.com/HpqG4Cxv

    Plugin Contributor alexgso

    (@alexgso)

    Hi Hunter,

    Thanks. The provided layout is working without issue for me. Does this issue occur if you disable all plugins except for SiteOrigin Widgets Bundle, and Elementor?

    Kind regards,
    Alex

    Thread Starter huntersbest

    (@huntersbest)

    Unfortunately no, strangely enough it is only a problem when logged out. AND only on the pages with the accordion.

    • This reply was modified 9 months, 3 weeks ago by huntersbest.
    Shane

    (@shanemarsh28)

    I can also confirm this issue is present in 1.58.5. We rolled back to 1.58.3 and all is OK again. Not sure what the cause is but here is the stack trace:

    2024/02/13 13:12:06 [error] 6498#6498: *2116 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in .../wp-includes/blocks.php:1188
    Stack trace:
    #0 .../wp-includes/blocks.php(1188): str_contains()
    #1 .../wp-includes/formatting.php(5226): filter_block_content()
    #2 .../wp-includes/class-wp-hook.php(324): wp_pre_kses_block_attributes()
    #3 .../wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #4 .../wp-includes/kses.php(946): apply_filters()
    #5 .../wp-includes/kses.php(754): wp_kses_hook()
    #6 .../wp-includes/kses.php(2171): wp_kses()
    #7 .../wp-content/plugins/so-widgets-bundle/base/inc/fields/base.class.php(384): wp_kses_post()
    #8 .../wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(759): SiteOrigin_Widget_Field" while reading response header from upstream, client: 70.132.38.37, server: <hidden>, request: "POST /wp-admin/post.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "<hidden>", referrer: "https://<hidden>/wp-admin/post.php?post=247&action=edit"
    
    Plugin Support Andrew Misplon

    (@misplon)

    Hi Shane, thanks for posting your error log. If you’d be willing to assist us further, perhaps you could get in touch via the contact page on our site.

    Thread Starter huntersbest

    (@huntersbest)

    With us, the problem seemed to be related to SO Widget: Accordion. Only pages with this widget were affected. I have to add, that not all widgets were used on site.

    I have resolved the problem for now by substituting another block.

    Plugin Support Andrew Misplon

    (@misplon)

    Thanks for the details; Alex is investigating.

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘Fatal Error 1.58.4 for NOT logged in users’ is closed to new replies.