Skip to content
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

Closed
3 tasks done
WuerfelDev opened this issue Jun 8, 2020 · 4 comments · Fixed by #931
Closed
3 tasks done

Upgrade from 0.4.6 to 0.7.0 #930

WuerfelDev opened this issue Jun 8, 2020 · 4 comments · Fixed by #931

Comments

@WuerfelDev
Copy link

Baikal version: from 0.4.6 to 0.7.0

  • I have searched open and closed issues for duplicates
  • I have installed the release zip, not the source code zip
  • I have moved the whole, untouched Specific folder to the new installation

Problem:

  1. backup old baikal folder
  2. replace with new baikal folder from 0.7.0 release
  3. bring back Specific folder
  4. Launch install in webbrowser:
    photo_2020-06-08_17-33-37
  5. fill form and continue
    photo_2020-06-08_17-33-47
  6. Finish installation after reloading the page
  7. Baikal reports as running but /html/admin/ shows this error:
    photo_2020-06-08_17-33-50
  8. DavDroid reports error 500:
    photo_2020-06-08_18-02-16

It's the same error as in #814 but I actually copied the whole Specific folder

@ByteHamster
Copy link
Member

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 Specific/config.php:

define("BAIKAL_INVITE_FROM", "noreply@$_SERVER[SERVER_NAME]");

@WuerfelDev
Copy link
Author

WuerfelDev commented Jun 8, 2020

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 Specific/config.php:

define("BAIKAL_INVITE_FROM", "noreply@$_SERVER[SERVER_NAME]");

The installation process worked fine, but still the errors in 7. and 8. persist.
Baikal 0.4.6 was working just fine before I upgraded PHP to 7.4

And the sqlite database looks like this:
Screenshot from 2020-06-08 19-31-21

@ByteHamster

This comment has been minimized.

@ByteHamster
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants