Upgrade Guide

Platform

---

• From v3.3.0 to v3.4.0
• From v3.2.0 to v3.3.0
• From v3.1.0 to v3.2.0
• From v3.0.0 to v3.1.0
• From v2 to v3

From v3.3.0 to v3.4.0

Recompile assets

Due to changes in core assets, you will have to recompile assets. You can do this with the following commands:

• npm install
• npm run dev

From v3.2.1 to v3.3.0

Recompile assets

Due to changes in core assets, you will have to recompile assets. You can do this with the following commands:

• npm install
• npm run dev

From v3.1.1 to v3.2.0

New way to register translations for VueJs

In order to let VueJS know about your translations you need to use the LoadingBackendTranslations hook to register your translations. This can be done like so in your module Service Provider:

$this->app['events']->listen(LoadingBackendTranslations::class, function (LoadingBackendTranslations $event) {
    $event->load('pages', array_dot(trans('page::pages')));
});

Recompile assets

Due to changes in core assets, you will have to recompile assets. You can do this with the following commands:

• npm install
• npm run dev

From v3.0.3 to v3.1.0

Recompile assets

Due to changes in core assets, you will have to recompile assets. You can do this with the following commands:

• npm install
• npm run dev

From v2 to v3

Upgrade to laravel 5.5

Follow the Laravel upgrade guide to upgrade your application and modules.

Re-publish configuration files

Using the following command you will be able to publish a module config files.

php artisan module:publish-config --force

If you edited the module configurations, you will need to manually copy over the new files, depending on what you changed, you can also publish each module individually.

Page translations

The page translation structure has been changed. Most keys are now at root level.
This should not impact you unless you published the translation files for page module.