Loading...
New plugin: bs TOC

Blog

Bootscore 6

Bootscore 5.4

Bootscore 6 stable is now available, offering exciting new features and useful improvements based on valuable feedback from v6-beta1 users.

Bootscore 6 stable is here, and users have downloaded v6-beta1 more than 3k times. Luckily, we got almost entirely positive feedback. We have fixed the reported issues and deeply tested v6 on production sites.

As announced in the v6-beta1 post, the theme has some minor adjustments and new features. Most installations will not be affected by these changes. However, if the AJAX cart is disabled by a filter, a second one is needed to enable the cart page. If the file template-parts/header/actions-woocommerce.php is overridden in the child theme, this file must be updated. For more details, take a look at the migration guide and view the changelog.

Skipped cart page

The offcanvas cart in v6-beta1 has received AJAX-loaded quantity buttons, which eliminates the need for an additional cart page. Coupons and shipping costs are calculated at checkout as well.

When something is added to the cart, only the “Checkout” button is displayed, shortening the customer’s path. The cart page is skipped, and the customer goes straight to checkout. The “Back to cart” button on the checkout page links to the shop instead of the cart page. The offcanvas cart is AJAX-loaded, so something must be added or removed from the cart to trigger AJAX and view the changes. Try it yourself:

Restore default behaviour

The cart page and the “View cart” button can be easily restored by adding a filter to the child-theme’s functions.php file:

add_filter('bootscore/skip_cart', '__return_false');

Now, the “View cart” button in the offcanvas cart is enabled and links to the cart page. The “Back to cart” button in the checkout links to the cart page.

editor-style, theme.json and block patterns

This may change the way you create landing pages and other content. In short, editor-style brings the compiled CSS to the Gutenberg editor, providing almost the same layout in the backend as in the frontend. The theme.json file removes the inner div in a group block and adds compiled color variables to the Gutenberg color palette. To use the color palette from theme.json in your existing child theme, add the new editor.scss file to the child theme’s /assets/scss/ folder.

Thanks to these two files, we created some block patterns that can be selected in the editor screen. These patterns include basic components like alerts, buttons, columns, and cards. You can combine and edit them to build your own elements or use prebuilt components such as heroes and sections.

Auto-updater

Last but not least, like all plugins, the theme now has an auto-updater, which updates Bootscore in the backend with a single click instead of uploading new versions zip file manually. Therefore, using the child theme is mandatory, as any update will overwrite changes made in the main theme. However, if you prefer to work on the main theme and, for example, create your own framework, here are instructions on how to remove the auto-updater.

New contributors

  • Thanks to stan1781 for fixing the empty Home value in breadcrumb.php.

Have a great day!

To top