Optimocha

@lorilself again, I’m afraid it’s their responsibility to provide a fallback. I wish I could be more helpful but I think you’ll see from our perspective: WooCommerce’s “cart fragments” are things that’s generated via the theme’s code, and each theme has a way to generate those fragments. In order for the Disable Cart Fragments (DCF) plugin to be compatible with all themes, I would have to install every WordPress theme, see how each generates their cart fragments (if it does generate any) and create a giant, million-line long compatibility class to ensure DCF is compatible with all themes.

The (correct) alternative is for each theme to simply don’t assume cart fragments are available at all times and maybe write a small compatibility class for DCF. In fact, checking the source code of the Astra theme (I assume you’re using Brainstorm Force’s Astra, which is a killer theme that I own a lifetime license of), I see that Astra has 24 different compatibility classes for different plugins. DCF could be the 25th.

There is one possible solution, or rather a workaround: You could hide that cart dropdown if the cart is empty, using the following CSS code:

.widget_shopping_cart:has(.widget_shopping_cart_content:empty){display: none;}

The cross-browser coverage of the has() selector isn’t perfect (around 90%) but it will get the job done with the most popular browsers.

Nice! And @thedelta if you liked our plugin (and got about four minutes), we’d love to have a fair review from you: https://wordpress.org/support/plugin/speed-booster-pack/reviews/#new-post

Nice catch, @thedelta!

And yep, we’ll definitely going to fix this for our next version! Any chance you could also test another bugfix in the lazy loader? We’re introducing an SVG placeholder that works better with themes (regarding image aspect ratios), as opposed to the GIF placeholder we’re currently using.

If you want to give it a test, here’s the latest version of the classes/class-sbp-lazy-loader.php file.

• This reply was modified 2 years, 5 months ago by Optimocha.

@monetenfuchs thank you for the correction! I submitted an issue to the Codestar Framework’s repository, which is a framework inside Speed Booster Pack: https://github.com/Codestar/codestar-framework/issues/171

When they update, we will update too. But you don’t have to worry as these are not actually errors, but depreciation notices.

Thank you so much for your kind words, @cagdasdag!

Thank you very much for your kind words, @foyzo!

@cloudduster unfortunately we implemented LiteSpeed caching as an experimental feature, but it caused more issues than we anticipated. If you like using Speed Booster Pack, we recommend you also install the LiteSpeed Cache plugin BUT only activate its caching-related features, and use Speed Booster Pack’s features except caching.

Hi @cloudduster, does the issue go away when you deactivate Speed Booster Pack?