Upgrade 0.6.1 to 0.7.1 doesn't work

[lje]

Baikal version: 0.6.1 ->0.7.1

• [x] I have searched open and closed issues for duplicates
• [x] I have installed the release zip, not the source code zip
• [ ] I have moved the whole, untouched Specific and config folders to the new installation Nope, there is no "config" folder in 0.6.1. I moved "Specific".

Problem:

I unzipped 0.7.1, moved the "Specific" folder (there is no "config" folder in 0.6.1) and started the installer. It asked me some questions (timezone etc.) and there was a slection to use MySQL instead of SQLite which I marked since I use MySQL. After the installer finished, when trying to open the admin-UI I got an error stating that table "calendarinstances" was missing. I checked the newly generated YAML file and noticed that it was set up for SQLite even when I marked "MySQL" in the installer. The whole MySQL configuration was missing in the YAML file and a new encryption key had been generated instead of using the old one.

I manually corrected the YAML file entering MySQL host/port/user and restored the old encryption key. Afterwards the admin UI worked.

I started Thunderbird to see if VCARD synchronization works, but got an HTTP 500 error listed in the sync log of Cardbook.

I gave up at this point and reverted to baikal 0.6.1.

[ByteHamster]

Do you have a stack trace for the 500 error? I am running Baikal 0.7.1 on my server and everything works fine.

[lje]

[13-Jun-2020 21:54:06] WARNING: [pool www] child 22149 said into stderr: "NOTICE: PHP message: LogicException: Requested uri (/dav/dav.php/addressbooks/xxx/default/) is out of base uri (/<server_name>/dav/dav.php/) in /var/www/virtual/xxx/baikal/vendor/sabre/http/lib/Request.php:184"

<server_name> is the DNS name of my server. For some reason it seems to become part of the path. I have baikal installed in a alternate document root and use "Rewritebase /" in .htaccess to fix that.

[ByteHamster]

Setting the base uri manually was removed in 0.7.0. Version 0.7.1 re-added that option. Try to play around with base_uri in config/baikal.yaml:

system:
    base_uri: '/dav/'

[lje]

That fixes the http 500 issue, thanks. The mentioned problems with the installer remain, I double checked in a second try. But these can be fixed by manually editing baikal.yaml.

One more remark: "configured_version" in section "database" wasn't filled by the installer as well. I guess what would be 0.7.1.

[ByteHamster]

One more remark: "configured_version" in section "database" wasn't filled by the installer as well. I guess what would be 0.7.1.

configured_version in section database is not used by Baikal. I will have a look why it is sometimes added to the file.

[MichiMunich]

I had the same behaviour as described by Ije. When I updated from 0.6.1 to 0.7.0 I had the error with the wrong or missing BaseURI. When I run the update from 0.6.1 to 0.7.1, the baikal.yml does not contain any MySQL settings but the installer assumes SQLite. I have now first updated to 0.7.0 and then to 0.7.1, defined the BaseURI in the baikal.yml and now everything works again. If I see it right, both lje and me are running our Baikal instances on an UberSpace host.

[beowulf222]

After upgrading to 0.7.1, I ran into the problem with the Base URI. In the new web interface, the option is no longer available to set it.

The error I received was Requested uri (/baikal/dav.php) is out of base uri (/ar/html/dav.php/)

What worked for me was setting the base_uri in config/baikal.yaml to the following: base_uri: 'baikal/'

I am using Apache as a webserver. I added a / to the end of the Directory path in my Apache Config as well, which wasn't there before <Directory "/opt/baikal-regular/html/">