Configuration files across modules has been changed, mostly the permissions.php 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.
Each module needs to handle config file loading
Previously the Core module did the configuration loading for every module. This responsibility has now been moved to every individual module. The reason is to have more flexibility on publishing modules configuration.
To register your configuration files, you can use a helper trait CanPublishConfiguration, with the publishConfig($moduleName, $filename) method. It takes the module name as first argument and the filename without extension as second.
Namespace change of Authentication and Setting interfaces
The Interface following interfaces that were previously under de Core namespace have been moved:
From : Modules\Core\Contracts\Authentication
Permission config file structure changes
The permssions system has been revamped in v2. On top of the UI changes, which has changed to display a way to inherit permissions. The permissions now also display a label.
This label is more user-friendly than the previous index, create etc permission names.
In order to update your permissions to allow this you need to add the perrmisions in a key -> value structure.