Upgrading to 3.7.0 From 3.6
Estimated Upgrade Time: 10 - 15 Minutes
We attempt to document every possible change. Since some of these changes are in obscure parts of the API only a portion of these changes may actually affect your application.
Before continuing please refer to the release notes to see more information on what has been changed.
composer.json file to match the 3.7 branch core addons and dependencies: https://github.com/pyrocms/pyrocms/blob/3.7/composer.json#L24-L84
Of course, don't forget to examine any additional addons and packages consumed by your application and verify you are using the proper version for PyroCMS 3.7 support.
Private Storage Adapter
The new Private Storage Adapter extension has replaced the
Local storage adapter due to general safety and aligning with future features around deployment automation.
You will likely want to keep the Local Storage Adapter when upgrading existing installations. Simply add the following to your
composer.json in the
require section after mirroring the 3.7
Update your configuration according to the following source files:
Disable Package Discovery for Laravel
Disable package discovery by appending your
composer.json file: https://github.com/pyrocms/pyrocms/blob/3.7/composer.json#L127-L131
Now that the
composer.json file has been brought up to speed we can let composer update our dependencies:
Install Search Module
Install the new Search module to fully replace the old TNT search driver.
php artisan addon:install search
Migrate the core as well as all installed addons:
php artisan migrate --path=vendor/anomaly/streams-platform/migrations/application php artisan migrate --all-addons
If your site uses a
messages.twig view partial then be sure to replace the
message_get functions with
It's a good idea to freshen up the entire system's caching and performance utilities:
php artisan refresh
Define Automatic Overrides
PyroCMS will no longer look through all addons for overridden views. You must define them in your theme or other addon using the
$overrides property or by using the
ViewOverrides collection directly.