Upgrade Guide

Upgrading an existing sprinkle from UserFrosting 4 to UserFrosting 5 can unfortunately be a difficult task. It all depends of how must customization of the core code you have done. Very basic sites will be easy to upgrade, very complex one could be a nightmare. However, it's for the greater good. UserFrosting 5 is more modern and uses new techniques

This guide contains the most important changes and action you need to take to upgrade your UserFrosting 4 Sprinkle. However, it's far from complete, as there are too many changes to document. Make sure you have a backup of your existing application and your development database before starting.

If you spot anything missing, don't hesitate to contribute to this page via the edit this page button at the top.

Before you start

The upgrade path for your UserFrosting 4 sprinkle will depend on how many features you're using. The good new is, the database structure is the same, and the frontend is 90% the same.

To begin the upgrade journey, the first you should do is a fresh install of UserFrosting 5. This is important, as it will allow you to familiarize yourself with the new structure, as well as validate that your local development environment is up to date and meet the minimum requirements.

Once you have a functioning vanilla version of UserFrosting 5, you can begin upgrading your sprinkle.

While the database structure is mostly the same between V4 and V5, it is highly recommended you keep a backup of your existing application and your development database.

Upgrading your sprinkle structure

As seen on the previous page, one of the biggest change is the app structure. It's recommended before you start to head over to Chapter 3 - App Structure, to learn more about this new structure.

Once you're familiar with the new structure, it's time to move thing around so your sprinkle meet the new structure. There's two options here : You can either start from scratch from the Skeleton repo, or you can manually upgrade in place.

The first option is easier as the base has been setup for you, and you can start right away moving your code into the skeleton created from the sprinkle template, in a new git repository. However, it's drawback is you'll probably lose your Git History. The second option is harder, but since you're starting from your existing code, you'll keep your git history if your code is saved on Github for example.

Option 1 - Start over from the Skeleton

To start with this option, the first step is to create a fresh install from the app skeleton. You'll then have an empty sprinkle with the new structure, ready to copy your code into it. However there's some step you need to follow before going further.

Update composer.json

The Skeleton comes with a basic composer.json. This defines the PSR-4 autoload namespace to UserFrosting\App\. You should edit this file to fit your sprinkle, as well as use the same namespace as your old sprinkle.

Important : To make sure your migrations and database data are preserved, the app namespace must be the same!

You'll also need to update the namespace in every existing class, index.php and bakery. See Customizing Your Sprinkle for more information.

Once this is done, you can run composer update to fetch dependencies.

Edit the Recipe

Next up you should familiarize yourself with the Sprinkle Recipe. Right now, the only thing you must update is the sprinkle name, but we'll come back later to the recipe.

Moving your code

Last part is to move your code from app/sprinkles/{YourSprinkle}/ from your old install (usually from app/sprinkles/{YourSprinkle}/) to app/ in the new directory.

At this point you can skip to Upgrading components

Option 2 - Upgrade in place

To start with this option, you should already be familiar with UserFrosting 5 directory structure, as it involves moving some directory around and editing some files. It also assume your code (your sprinkle) was located (and not as a community Sprinkle for example) You should have UserFrosting 5 Skeleton repo on hand to copy some files.

Moving files and directory

  • Delete :
    • composer.json
    • bakery
    • build/
    • vagrant/
    • public/index.php
    • app/system/
    • app/tests/
    • app/defines.php
    • app/.htaccess
    • app/sprinkles/account/
    • app/sprinkles/admin/
    • app/sprinkles/core/
    • app/sprinkles.example.json
    • app/sprinkles.json
  • Move everything inside app/sprinkles/{YourSprinkle}/ to app/, and delete the empty app/sprinkles/ directory.
  • Copy from the skeleton, replacing existing files :
    • /public/index.php
    • /bakery
    • /package.json
    • /webpack.config.js
    • /webpack.entries.js
    • docker-compose.yml
    • docker/
    • .gitignore

Updating composer.json

In UserFrosting 4, your composer.json was located in app/sprinkles/{YourSprinkle}/composer.json. It was merged with the main composer file and the dependent sprinkles on build. With UserFrosting 5, there's only one composer.json: Yours. And it lives in /composer.json.

This step requires you to merge your composer.json with UF5's. Start by moving your file, which should now be located at /app/sprinkles.json to /composer.json.

Next, you'll need to update some dependencies. Open composer.json from the skeleton, and copy every dependencies from required and require-dev from it to your composer.json.

You should also update the path for the autoload and autoload-dev section to point to app/src/ and app/tests/ respectively.

Important : Don't change the namespace if you want to keep the existing migration!

Once this is done, you can run composer update to fetch dependencies.

The Recipe

The next step is to create your sprinkle recipe.

Start by :

  • Copy app/src/MyApp.php from the skeleton into your app, inside app/src/
  • You can rename MyApp to whatever you want. Simply don't forget to adapt the next steps with the name you chose.
  • Change the namespace inside your app/src/MyApp.php to the namespace you use in your composer.json

We'll update the rest of your recipe later.

The entry files

Finally, you'll need to update both entry files, aka /bakery and /public/index.php, with the correct reference to your recipe. Open both files, and replace UserFrosting\App\MyApp and MyApp with the correct reference to your recipe. See this page for more information and example.

Upgrading components

At this point your UserFrosting 5 app is kind of ready to work. You simply need to upgrade every component your use. The following list might contains stuff you're not using, but you should still go through them as they contains links and tip you may need later.

Remember, this guide will give you only the big picture of what changed, pointing you to other part of the guide that goes in details with all the features.

Global changes

It's important to note some changes have been applied at large, and affect pretty much every PHP class, based on PHP 8 new features. These changes include:

Keep this in mind, especially if you've extended built-in classes. Not only may these classes been renamed or moved, the method declaration might have changed even if the code of these method haven't.

Services -> Dependency Injection

Services have been updated for UserFrosting 5. While the principle is the same, the way to register service is different. Services are now served by the new dependency injection container, PHP-DI. You should head over to the Dependency Injection Chapter to learn more about PHP-DI integration in UserFrosting 5 before going further.

Your services definition must first be updated to implement UserFrosting\ServicesProvider\ServicesProviderInterface. For example:


class ServicesProvider
    public function register(ContainerInterface $container)
        // ...


use UserFrosting\ServicesProvider\ServicesProviderInterface;

class ServicesProvider implements ServicesProviderInterface
    public function register(): array
        return [
            // ...

You'll also need to register your service in your recipe. Checkout Adding Services for more information.

Finally, instead or injecting the whole container and retrieving your service from it, your should inject the service directly into the class using autowiring in the class constructor or thought route service injection for example.

For example:


public function __construct($ci)
    $this->camHelper = $ci->camHelper;


public function __construct(protected CamHelper $camHelper): void



The classmapper has been removed in UF5. PHP-DI should be used instead, via the "autowire" and interface binding. Existing classmapper definition should be moved inside a service, and call to the classmapper should be updated to use dependendy injection via the controller or other method.


Migration are mostly the same, only the class structure as changed, as well as the need to register migration in your Sprinkle Recipe. The key points regarding migration are as follow :

  1. Up/Down return type : The up() and down() method must now return void

  2. Migration must now implement UserFrosting\Sprinkle\Core\Database\Migration. Change use UserFrosting\System\Bakery\Migration; to use UserFrosting\Sprinkle\Core\Database\Migration; in every one of your migrations.

  3. Dependencies must now be declared in a static property. Change public $dependencies = []; to public static $dependencies = []; in every one of your migrations.

  4. Migration are not auto-discovered anymore. You need to add them to your sprinkle recipe, using MigrationRecipe. See the migration chapter for more information and a detailed guide.


The only change in database model is the $timestamps property is not true by default. It used to be false. public $timestamps = true; can be removed from your models, unless you're not using timestamps where you should add public $timestamps = false;.


The way to register route as changed. The definition is mostly the same, however the routes are now a real PHP classes, instead of static php resources. Check out the Registering routes guide for more information.

To updated your routes, you should start by :

  1. Move your routes from app/routes/* to app/src/Routes/*;
  2. Update your routes definitions so it's a class implementing RouteDefinitionInterface
  3. Register your routes in your Sprinkle Recipe.

A few other key point to know:

  1. Route groups definition has changed. See Slim Documentation for more information
  2. Controller resolution should be updated to make use of PHP’s ::class operator
  3. Middleware must now be called by their class name. For example, authGuard must be updated to UserFrosting\Sprinkle\Account\Authenticate\AuthGuard::class


The sprunje class used to accept options in the constructor. To make it easier to inject dependencies, options should now be defined using the setOptions method. Sprunje should now be injected into controllers,


public function camsList(Request $request, Response $response, array $args)
    // GET parameters
    $params = $request->getQueryParams();

    /** @var /UserFrosting\Sprinkle\Core\Util\ClassMapper $classMapper */
    $classMapper = $this->ci->classMapper;

    /** @var \UserFrosting\Sprinkle\Core\Router $router */
    $router = $this->ci->router;

    $sprunje = new CamsSprunje($classMapper, $params, $router);

    return $sprunje->toResponse($response);


public function camsList(Request $request, Response $response, CamsSprunje $sprunje): Response
    // GET parameters
    $params = $request->getQueryParams();

    return $sprunje->setOptions($params)->toResponse($response);

This also mean the Classmapper is not available anymore in sprunjes. You should inject the necessary classes and services into your sprunjes.


Simple changes have been made to controller classes :

  1. Remove extends SimpleController, no extension is required anymore.
  2. use Slim\Http\Request; must be changed to use Psr\Http\Message\ServerRequestInterface as Request;
  3. use Slim\Http\Response; must be changed to use Psr\Http\Message\ResponseInterface as Response;
  4. Since the DI container is not available globally in controllers, the services you requires must be injected in constructor
    1. For example, to use the view service, inject Slim\Views\Twig;

See Controller classes guide for more information.

[note]If your sprinkle extends a controller class from a default sprinkle instead of SimpleController, note that every controller classes from default sprinkles have been moved, renamed and rewritten as Action classes. Make sure to check out the sprinkle source code to find out how to update your sprinkle.[/note]


Simple changes have been made to bakery commands :

  1. Command must extend Symfony\Component\Console\Command\Command instead of UserFrosting\System\Bakery\BaseCommand
  2. Service should be injected through the class constructor (don't forget to call the parent constructor) or via attribute injection.
  3. Add use UserFrosting\Bakery\WithSymfonyStyle; Trait to access $this->io
  4. Command should return return self::SUCCESS; or return self::FAILLURE;

The biggest changes is you're now required to register your command in your sprinkle recipe. Check out Bakery CLI chapter for more information.

Also note that the create-admin command has been renamed create:admin-user. If your were adding custom command to "bake" command, you can now use the Extending Aggregator Commands guide to achieve this more easily.

Resources Stream / Locator

Not must as changed regarding the Resource Locator. Refer to the Locator Service page for more information. Note however that the two stream below have been renamed:

  1. log -> logs
  2. session -> sessions


Three points are to be considered when working with templates:

First, sprinkles have been renamed. If you're extending a default sprinkle, you'll need to update the sprinkle reference in the extends tag. For example: {% extends "@admin/pages/activities.html.twig" %} => {% extends "@admin-sprinkle/pages/activities.html.twig" %}. Check the table below for a list of sprinkle identifier.

Name Slug
Admin Sprinkle admin-sprinkle
AdminLTE Theme adminlte-theme
Account Sprinkle account-sprinkle
Core Sprinkle core-sprinkle

In a similar way, some Twig templates have been moved to the "AdminLTE" sprinkle. Be sure to check the new structure if you're extending templates with the extends tag. Some templates file previously in the Admin Sprinkle might be in the AdminLTE sprinkle now.

FontAwesome has also been updated, and references to icon must also be updated : fa -> fas


  1. Facades (Translator, etc.) are no longer available. The corresponding service should be injected properly now.
  2. Router PathFor has been changed. To generate a route based on it's name, inject Slim\Interfaces\RouteParserInterface and use urlFor method.
  3. Exceptions have changed, especially HTTP ones. For example : use UserFrosting\Support\Exception\ForbiddenException; => use UserFrosting\Sprinkle\Account\Exceptions\ForbiddenException; Check out Exception and Error Handling guide for more information.

Login redirect

If your sprinkle was implementing a custom post-login destination, be sure to check out the updated recipe.


If your sprinkle had automated testing :

  1. Create a new Sprinkle Test case
  2. setupTestDatabase has been removed, it's no longer necessary
  3. UserFrosting\Sprinkle\Core\Tests\RefreshDatabase is now UserFrosting\Sprinkle\Core\Testing\RefreshDatabase
  4. TestDatabase is removed
  5. withTestUser usage has been updated
  6. Factories have been overhauled


Asset management have been completely changed. Instead of a custom solution, UserFrosting 5 now uses Symfony's Webpack Encore to handle and build frontend assets. Your first stop should the Asset Chapter or the documentation for in-dept guide for this new system.

The key points here are :

  1. Your asset-bundles.json must be replaced with a new entrypoint and entries.
  2. Rendering of assets (css and js entries) must be updated. Checkout the content/scripts_site.html.twig and content/stylesheets_site.html.twig files from the skeleton repo for an example.
  3. Static assets must be copied to the built directory