I got an error when installing 2.0.16, error is in
postUpdateCmd. No User plugin was installed and obviously, the following migration fails. I tried the migration on two different environments (development on Mac with MySQL, stage on Linux with Postgres), same error on both.
> php artisan october:install .... > System\Console\ComposerScript::postUpdateCmd In Plugin.php line 87: Class 'RainLab\User\Models\User' not found In Plugin.php line 87: Class 'RainLab\User\Models\User' not found .~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~. ,@@@@@@@, ,,,. ,@@@@@@/@@, .oo8888o. ,&%%&%&&%,@@@@@/@@@@@@,8888\88/8o ,%&\%&&%&&%,@@@\@@@/@@@88\88888/88' %&&%&%&/%&&%@@\@@/ /@@@88888\88888' %&&%/ %&%%&&@@\ V /@@' `88\8 `/88' `&%\ ` /%&' |.| \ '|8' |o| | | | | |.| | | | | `========= INSTALLATION COMPLETE ========='
It looks like you may be missing the RainLab.User plugin, please run
php artisan plugin:check to make sure all dependencies are installed.
I hope this helps!
The check says what's known:
php artisan plugin:check In Plugin.php line 87: Class 'RainLab\User\Models\User' not found
In the guide it stands:
If you have any non-vendor plugins that you have developed yourself, copy them across as well.
Nothing about vendor plugins. Yes, one of my plugins is actually dependent on Rainlab.User and I expected Rainlab.User to be installed automatically because in my Company\MyPlugin\Plugin.php it says
public $require = ['RainLab.User'];
Do I have to install the User plugin manually before I start the installation or at least do I have to edit the composer.json dependencies by hand?
Yes. Install with composer:
composer require rainlab/user-plugin
Should do the trick.
OK, I managed it somehow. I did not copy our plugins to the new installation at the beginning of the migration. I did the migration, then copied our plugins and did the plugin sync.
October 2.0 works, but I don't see any way how to migrate the data from the database, which is understandable because the migration process has no information about the original database. Obviously, we have to re-enter all backend users, mail templates and many, many other settings manually. All this on developer, stage and production servers. I don't see any benefits of migration for existing installations that just work. However, I assume that no bugs will be backported to version 1.0.x, so there is probably no alternative. It can be a pretty expensive migration.
1-5 of 5