-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from 0.4.6 to 0.7.0 #930
Comments
I can confirm that this is a bug in 0.7.0 that occurs when upgrading from <0.6.0 to 0.7.0. Until this is fixed, you can use a workaround. To work around the error, basically do the same upgrade procedure that you already did (copying Specific folder) but before you open the admin interface for the first time after upgrading, add the following to the new
|
The installation process worked fine, but still the errors in 7. and 8. persist. |
This comment has been minimized.
This comment has been minimized.
Oh, I'm sorry. I just tried to upgrade from an older version and can confirm your issue. The notification rework does not upgrade the database. Try to upgrade to 0.6.1 first and then from 0.6.1 to 0.7.0. This will be fixed as soon as possible. |
Baikal version: from 0.4.6 to 0.7.0
Specific
folder to the new installationProblem:
It's the same error as in #814 but I actually copied the whole Specific folder
The text was updated successfully, but these errors were encountered: