Home>Support>Reusable Blocks – Gutenberg / SiteOrigin Widget

Reusable Blocks – Gutenberg / SiteOrigin Widget

Hi,

I am having an issue with the SiteOrigin Widget Bundle. When creating new posts, I use a reusable block. Recently I have not been able to use these blocks. After a bit of troubleshooting, I have discovered that if I turn off the widgets bundle I can use the reusable blocks but once I turn it back on I cannot.

Is this a known bug?

Appreciate any support you can give.

Thanks

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Hi TheStoicTrader

    Thanks for reaching out.

    I ran a quick test locally and I can use a reusable block with the Widgets Bundle activated or the Widgets Bundle used in the block.

    Are there any console errors in red text when the issue occurs? Here is how you can check: https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. If there are, please, take a screenshot, upload it to imgur.com or any sharing site and send us the link.

  2. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Thanks for the reply. Below is a link to the error received when opening the block section.

    https://imgur.com/a/I3yy93e

    If you need anything else, let me know.

    Thanks

    TheStoicTrader

  3. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks for the screenshot. Does the 500 error persist if the Widgets Bundle is the only plugin activated?

  4. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    No, it works OK with only the widgets bundle activated. Would you suggest leaving on the WB and turning on each plugin one by one?

  5. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    If possible, yes, that would be great. If you have a lot of plugins installed then you could split the plugins screen up into four parts and reactivate your plugins in blocks to try and narrow down which plugin is causing the issue.

  6. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Lucky my list of plugins isn’t too big. Having turned them all off / on, the only time the error occurs is when the Widget Bundle and the Page Builder are turned on together. When the Widget Bundle is on by itself there is no error, likewise when the Page Builder is on by itself but when they are on together the 500 error occurs.

  7. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks. To confirm, the issue occurs with Page Builder and the Widgets Bundle activated with no other plugins activated?

  8. 1 year, 4 months ago TheStoicTrader

    Yes, those are the only two active plugins when the error occurs.

  9. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks. Please, could you trying sending the console log containing the 500 error to hosting support and kindly ask if they can take a look? Please, ask them if they can perhaps check ModSecurity logs or similar to see if there is anything related showing up there, perhaps as a false positive?

  10. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Will do. Will pass along their response. Thanks for the support.

  11. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks. Please, let us know how it goes.

  12. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Support have confirmed it is not a security-related issue. They have provided me with the error that occurs, hopefully this will shed some light. They mentioned that it seems like the code is expecting a number but is getting text as a return resulting in the error.

    PHP Fatal error: Uncaught Error: [] operator not supported for strings in /wp-content/plugins/so-widgets-bundle/base/inc/post-selector.php:106

  13. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Thanks for the error info. Please, could you send us a copy of the block? Here is how https://www.pair.com/support/kb/gutenberg-editor-how-to-access-the-code-editor/. If you could upload the contents to a file on Dropbox/Drive or WeTransfer.com, that would be great. Pastebin.com is another option.

  14. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Do you need each reusable block or will one do? No reusable blocks are visible.

    Thanks

  15. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Any reusable block that’s involved in the issue will do. We’ll attempt to recreate the issue locally. If they aren’t visible, could you perhaps export the Widget Block/s that are in the reusable and we’ll make our own reusable?

  16. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Does this perhaps help? https://www.wpbeginner.com/beginners-guide/how-to-create-a-reusable-block-in-wordpress/#:~:text=Exporting%20%2F%20Importing%20Reusable%20Blocks&text=You%20can%20export%20the%20blocks,another%20WordPress%20site's%20admin%20area.

  17. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Apologies for the delay. I have transferred one of the blocks to wetransfer, link below.

    https://we.tl/t-tSYZGn6Xed

  18. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Super, thanks.

    For interest sake, in the Attributes tab, the closing semi-colon ; isn’t required when adding CSS declarations.

    color: red

    Is no problem.

    In the Post Loop widget, post__not_in doesn’t support the string syntax and must be used in an array. It, unfortunately, can’t be used in the Additional field. Is there any improvement if you clear the Additional field?

    I’m not aware of a method to exclude a single post using query_posts. You could add a category for the post and then use:

    cat=-x

    Or perhaps select only the taxonomies you’d like to display using the Taxonomies field.

  19. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    I’ve corrected the above: “For interest sake, in the Attributes tab, the closing semi-colon ; isn’t required when adding CSS declarations.”

  20. 1 year, 4 months ago TheStoicTrader

    Hi Andrew,

    Again, thanks for the response. As you can probably tell, I have very little coding experience and am flying by the seat of my pants. As such, the post__not_in function was the only thing I could get to work (I wanted to exclude the current post from the related posts section).

    I have not made any changes to the blocks as of yet, but I have just updated page builder to 2.11.3. As of a few moments ago, I can now access the reusable blocks with both plugins enabled.

  21. 1 year, 4 months ago Andrew Misplon Hi, I Work Here

    Super, thanks for the update. There were block data validation improvements in the update. Glad to hear that’s helped.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More