UserFrosting 4.2 brings improved organization of the codebase, a new migrator and seeder as well as improved assets management.
migrate:status Bakery commandsprinkle:list Bakery commandtest:mail Bakery CommandNoCache middleware to prevent caching of routes with dynamic contentmigrate and migrate:* Bakery command now require confirmation before execution when in production mode.withRaw, withSum, withAvg, withMin, withMax (see https://github.com/laravel/framework/pull/16815)create-admin and setup Bakery commands so it can be used in a non-interactive way (#808)filesystem service (#869)Seeder and seed Bakery commandwithTestUser trait for helper methods when running tests requiring a userControllerTestCase special test case to help testing controllersphpunit.xml.php_cs) and instructions for PHP-CS-Fixer in Readmeroute:list Bakery commandio property from migration classes. The console IO instance is not available anymore in migrationsprojectRoot property. Use the \UserFrosting\ROOT_DIR constant insteadUserFrosting\System\Bakery\DatabaseTest trait for custom Bakery command, use UserFrosting\Sprinkle\Core\Bakery\Helper\DatabaseTest instead.UserFrosting\System\Bakery\ConfirmableTrait trait for custom Bakery command, use UserFrosting\Sprinkle\Core\Bakery\Helper\ConfirmableTrait instead.UserFrosting\Sprinkle\Core\Database\Migration instead of UserFrosting\System\Bakery\Migrationseed method. Database seeding should now be done using the new Seeder.\UserFrosting\Tests\DatabaseTransactions has been deprecated. Tests should now use the \UserFrosting\Sprinkle\Core\Tests\DatabaseTransactions trait instead. (#826)semantic versioning part of a migration class optional. Migrations classes can now have the UserFrosting\Sprinkle\{sprinkleName}\Database\Migrations namespace, or any other sub-namespaceUserFrosting 4.2.x now requires Node.js 10.12.0 or above and NPM 6.0.0 or above.
To update Node.js and NPM on most UNIX system, you can use the n NPM Package :
sudo npm cache clean -f
sudo npm install -g n
sudo n -q ltsThis will install the latest LTS (Long Term Support) version of Node.js.
Bower has been deprecated since 2017, and with NPM support landing in UserFrosting, Bower is now deprecated here as well. In the future, support for it will be removed.
Frontend dependencies used by UserFrosting are now retrieved from NPM. If you depend on these you may find certain files have shifted around, verifying references are correct is recommended. UserFrosting can help in this endeavor, as missing resources referenced using the locator infrastructure will produce a server error.
To facilitate an easier transition and accommodate the complexities associated with the node module resolution logic that permits duplicate indirect dependencies, compatible main entry points will be run through Browserify to resolve require imports.
Dependency conflicts between individual sprinkles for bower.json may now occur. If this occurs you'll need to update the semver range to resolve or force a specific version using the resolutions attribute.
Finally, frontend dependencies are now located at app/assets/bower_components for Bower and app/assets/node_modules for NPM. Running php bakery assets-install will automatically remove dependencies in the old location. This does not affect asset resolution.
As of UserFrosting 4.2.0, support for PHP version 5.6 and 7.0 is officially deprecated. While you can still use UserFrosting 4.2.x with PHP 7.0 or earlier, upgrading to PHP 7.2 or above is highly recommended as both PHP 5.6 and 7.0 have reached End Of Life since Jan. 1st 2019.
See the Changelog for the complete list of changes included in this release.
Upgrading UserFrosting to 4.2.x is as simple as getting the new files and updating dependencies, migrations and assets! If you first installed UserFrosting using git, a simple git pull or git pull upstream master. Once you have the new files, simply use composer and Bakery to get up to date with everything else:
$ composer update
$ php bakery bakeSince Bower is now deprecated, it is recommended to migrate your sprinkle third party frontend dependencies to Yarn. This can be accomplished by renaming your sprinkle bower.json file to Yarn's package.json.
Some package can be named differently between Bower and Yarn. For example, the Bootstrap 3 Typeahead package is named bootstrap3-typeahead in Bower, but bootstrap-3-typeahead in Yarn. Refer to Yarn website to see if your sprinkle third party dependencies need updating.
Migrations should be updated to extends UserFrosting\Sprinkle\Core\Database\Migration instead of UserFrosting\System\Bakery\Migration. Migration that have already been run don't need to be run again.
Any migrations using the io property to interact with the user through the command line needs to be updated. Since migrations can now be run outside of the CLI, migrations can't make use of the io anymore. Any task requiring user input should be moved to a custom Bakery command or seed.
Finally, the $dependencies property should now be static. Non-static property will still work, but the support for it is deprecated which means it might be removed in a future update. To make sure your migrations are compatible with future version, simply change public $dependencies = [ ... ]; to public static $dependencies = [ ... ]; in your migration file. This can also be applied safely to migrations which have already been run, as it doesn't affect the data or table structure.
Database seeding should now be perform using the new Seeder class and seed bakery command. This new seeder allows for multiple seeding, detached from the migration system. It can also be used along Unit Tests.
Seeding performed in migrations will still work, but support for database seeding inside migrations will be removed in future versions. See the Database Seeding documentation on how to move your seeds to the new Seeder class.
If assets installation fail, simply delete the build/package-lock.json file and the build/node_modules/ directory. You can then run the Bake or build-assets command again.
Due to changes in the logic used to load migrations classes in 4.2, the order in which they are run may differ from previous releases. This may result in new foreign key constraint errors. If this happens in your own custom migrations, it may be a sign of missing dependencies (Those migrations working under 4.1 may just be a coincidence!)
To fix this, make sure your migrations define the appropriate dependencies. Also make sure those dependencies are up to date. You might also want to change the $dependencies property to a static one at the same time. Don't hesitate to seek help if you need assistance on this or encounter a different migration related issue.