Bootscore v6 is here! Learn more
Account
Cart

No products in the cart.

Documentation Theme

Migration

Track and review changes to Bootscore’s files helping you to migrate from v5 to v6.

v6.0.0-beta-1

While it’s build from v5, almost all files have been changed/moved or have a new name, fallbacks for deprecated functions have been deleted. In conclusion, v6 is a new theme. For a complete list what’s changed, take a look to the changelog.

Installation folders from parent-theme and child have been removed -main suffix in folder name. Means that installing v6 themes will not replace existing v5 ones.

With this in mind, the optimal approach is to begin with a new child theme and gradually transfer your work from the v5 to the v6 child theme, checking each change in the frontend as you progress.

Migrations should always be performed on a backup site and should never happen on a live project.

Depending on the size of your project and the number of templates you have overridden in your child theme, migration may take some time. For small to mid-sized projects, it’s possible to migrate within 30 minutes to 1 hour starting with a new child.

Here is a list of all the points you need to consider when copying files or code into your new child theme. Note that:

  • Breaking labeled items must be resolved, otherwise there will be conflicts with the compiler or a PHP error or which leads into the White Screen of Death (WSoD).
  • Warning labeled items might disturb your layout but do not crash the site.

Changes

  • Breaking The folders scss, js, and img have been moved from the root location into the assets folder. Compiled CSS will be created now in /assets/css/main.css. As a result, the enqueue script in the child theme has been modified. If you have Google fonts installed as described here, move fonts folder into assets as well.

  • Breaking The Bootstrap source is now loaded in parts, enabling the addition of new _bootscore-utilities.scss. Bootscore’s .scss files have been renamed from for example _bscore_custom.scss into _bootscore-custom.scss for better clarification. Take a look to the child’s main.scss to check how they are imported. Rename your modified files as well and update child’s main.scss.

  • Breaking Deleted emtpy Internet Explorer fallback function. Open header.php, scroll down to the bottom and check if <?php bootscore_ie_alert(); ?> still exists. Delete it.

  • Breaking Deleted hook after_primary. This affects all content templates like page-*.php, single-*.php, archive-*.php, category-*.php, search.php etc. Open these files and check if <?php bs_after_primary(); > exists. Delete it. If you are using the Isotope CPT, delete this there as well or download the updated version.

  • Breaking Replaced <?= bootscore_container_class(); ?> with a filter for more flexibility. This affects all templates where a container is present. Replace entire snippets with class container.

  • Breaking Replaced <?= bootscore_main_col_class(); ?> with a filter for more flexibility. This affects all content templates like page-*.php, single-*.php, archive-*.php, category-*.php, search.php etc. Replace string with <?= apply_filters('bootscore/class/main/col', 'col'); ?>.

  • Breaking Replaced <?= bootscore_sidebar_col_class(); ?> with a filter for more flexibility. This affects sidebar-*.php. Replace string with <?= apply_filters('bootscore/class/sidebar/col', 'col-lg-3 order-first order-lg-2'); ?>.

  • Breaking Replaced <?= bootscore_sidebar_toggler_class(); ?> with a filter for more flexibility. This affects sidebar-*.php. Replace string with <?= apply_filters('bootscore/class/sidebar/button', 'd-lg-none btn btn-outline-primary w-100 mb-4 d-flex justify-content-between align-items-center'); ?>.

  • Breaking Replaced <?= bootscore_sidebar_offcanvas_class(); ?> with a filter for more flexibility. This affects sidebar-*.php. Replace string with <?= apply_filters('bootscore/class/sidebar/offcanvas', 'offcanvas-lg offcanvas-end'); ?>.

  • Breaking Nav-walker has been moved from an own enqueued file into a pluggable function. Breaking if you have registered an own modified nav-walker for example allowing more then 2 levels.

  • Warning Main content col breakpoints have been changed from md to lg. This affects all content templates like page-*.php, single-*.php, archive-*.php, category-*.php, search.php etc. and sidebar.php.

  • Warning Navbar has been refactored from fixed-top to sticky-top. As a result, all content template spacers have been changed from py-5 mt-5 to pt-4 pb-5. This affects all content templates like page-*.php, single-*.php, archive-*.php, category-*.php, search.php etc.

  • Warning Widgets supports now Gutenberg. Existing widgets have been moved into legacy widgets by WordPress. This is not urgent, but they should replaced by Gutenberg widgets step-by-step.

  • Warning The card wrapper in sidebar widgets has been removed for better Gutenberg integration. Follow this instruction to restore the card in sidebar widgets.

To top