Using [SSB] no longer working in Widget area
-
Hi, been using SSB for 5 years now (in a classic theme scenario) with a really simple setup:
1) Chose the button design I like
2) Didn’t select any position options
3) Used the [SSB] shortcut in “Widgets” in our right sidebar which gave us the fully functioning icons
Since the latest upgrade the buttons do not load in the sidebar properly unless a position option is selected (i.e. “Inline”) and posts & pages is selected. They appear on the sidebar but are unstyled and non-functioning unless they are “positioned” first through settings.
Is there any way to restore the previous functionality so the buttons can work solely in a widget area?
Thanks for your time
-
I also came across this issue.
You can force the front-end assets to load with a filter (add to functions.php or a code snippet plugin):
add_filter( 'ssb_enqueue_front_assets', '__return_true' );I think there should be an option in the plugin settings to enable this though.
Hello @stevieboy23,
Thanks for bringing this to us! Just wanted to let you know that yes, the filter shared by @commareus will work as a temporary workaround, but we’ve actually fixed this issue on our end already.
For early access please raise a support ticket in our support forum to get access to the beta version with the fix.
Thanks again for your patience!
Hi @stevieboy23 ,
That completely made our day, thank you!
Just checking in as well, if you’re still keen to get ahead of things with the beta build that includes the fix, we’re happy to send it your way whenever suits you.
Just let us know!I should have clarified that we’re not using the shortcode in a widget, we’re calling it directly from the theme using do_shortcode() — will the fix in the beta solve the issue in this scenario too?
Thanks, I have done as you suggested, followed your link and requested the beta version – many thanks!
Hey @commareus,
Yes! the fix in the beta also covers your scenario.Beta installed and fully working – thank you!!
Hey, @stevieboy23 and @commareus!
Thank you both so much for your patience, support, and kindness throughout this thread; it really means a lot to us! We’re thrilled to hear that the beta build resolved the issue on your end.
Just wanted to let you know that we’ve now officially rolled the fix into release 7.1.0, which is live. So you’re all set to update to the stable version whenever it’s convenient; no need to stay on the beta any longer.
Thanks again for reporting the issue and helping us test the fix. Wishing you both a great day!
You must be logged in to reply to this topic.