Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
- Fixed a critical bug that broke the theme
- Updated README for 8.x branch, people who want to manually create the subtheme (not advised: use Drush) now have all the needed step to make it work.
- It is encourage to put neato in /themes/contrib now and the child theme is automatically created in /themes/custom when using the drush command to create a child theme.
- Cleaned out templates.
- Colors and breakpoints are now in separate scss files to keep the child theme easier to maintain.
- Changes to README and installation notes
Fixes an issue where page--front example template was not served on sites that had no defined nodes. Changed to page template instead, to ensure it is displayed as an example.
Cleaned up the Gulpfile and removed browser sync reloading for now as it's functionality was flakey at best. Browser sync is now a seperate task, not triggered with watch, so for folks not wanting to use it, it stays out of the way.
Tweaked how breadcrumbs are included, the STARTER subtheme has the SCSS under 'components' now.
If you are trying to get breadcrumbs to show up in Drupal 8, you now need to provide paths - system routes (eg node/4) won't show a breadcrumb even if it is a child of other nodes in the menu. Installing Pathauto and Token is advised, and most people will do this anyway.
Updating tag to match core compatibility pending 8.0 core release.
Updates the package.json to include the most recent version of gulp-sass instead of use a git:// URL which may not always work on Windows. Also adds the npm "rimraf" package so that a universal postinstall script command can be used on either Windows or OSX/Unix to eliminate .info files from the node_modules folder.
Updates the package.json to include the most recent version of gulp-sass instead of use a git:// URL which may not always work on Windows. Also adds the npm "rimraf" package so that a universal postinstall script command can be used on either Windows or OSX/Unix to eliminate .info files from the node_modules folder.
This release addresses a critical bug related to Drupal core's handling of .info files and its assumption of them being in a theme folder.
The package.json file will now execute a command after installing that will remove any .info files from the node_modules folder to avoid this segfault until it is addressed properly in Drupal core. Otherwise the Gulpfile won't run, and Drupal will return a segfault when trying to access it (as will Drush.
If you want to remove them yourself, enter this command in shell from the proper directory path to your theme:
This release addresses a critical bug related to Drupal core's handling of .info files and its assumption of them being in a theme folder.
The package.json file will now execute a command after installing that will remove any .info files from the node_modules folder to avoid this segfault until it is addressed properly in Drupal core. Otherwise the Gulpfile won't run, and Drupal will return a segfault when trying to access it (as will Drush.
If you want to remove them yourself, enter this command in shell from the proper directory path to your theme: