no such table: calendarinstances after upgrading from 0.4.6 to 0.7.0 same as #810

[Andrewskiz]

Baikal version: 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 and config folders to the new installation

Problem:

So I just upgraded from 0.4.6 to 0.7.0 and I am getting the same error as issue #810

PDOException: SQLSTATE[HY000]: General error: 1 no such table: calendarinstances in /home/public/baikal/Core/Frameworks/Flake/Core/Database.php:191
Stack trace:
#0 /home/public/baikal/Core/Frameworks/Flake/Core/Database.php(191): PDO->query('SELECT count()...')
#1 /home/public/baikal/Core/Frameworks/Flake/Core/Requester/Sql.php(215): Flake\Core\Database->query('SELECT count()...')
#2 /home/public/baikal/Core/Frameworks/BaikalAdmin/Controller/Dashboard.php(51): Flake\Core\Requester\Sql->count()
#3 /home/public/baikal/Core/Frameworks/Flake/Core/Render/Container.php(69): BaikalAdmin\Controller\Dashboard->render()
#4 /home/public/baikal/Core/Frameworks/Flake/Controller/Page.php(90): Flake\Core\Render\Container->renderBlocks()
#5 /home/public/baikal/html/admin/index.php(90): Flake\Controller\Page->render()
#6 {main}

I am using SQLite, PHP 7.2, and I did not overwrite the Specific folder (the config folder did not exist). I opened the baikal/html/admin/ and ran the install / upgrade script, which seemed to go fine but it didn't ask me to upgrade anything related to the database. Now I can no longer access the admin panel, and DAVx5 throws an error 500 each time it updates.

Thanks for the help!

[ByteHamster]

Hi,

Version 0.7.0 currently has a bug that only allows upgrading from 0.6.1. For other version, it forgets to do the database migrations. The easiest solution is to first upgrade to 0.6.1 and then to 0.7.0. The upgrade issue was fixed in #931

No guarantee but it could work to set configured_version: 0.4.6 in baikal/config/baikal.yaml. Make a backup of the database (or even the whole directory) first. After setting this, the admin interface should ask for database migrations.

[Andrewskiz]

Will there be any issue overwriting everything again and upgrading to 0.6.1, since it already attempted to upgrade to 0.7.0? I have a backup, but I don't want to make things any harder than I have to.

[ByteHamster]

Will there be any issue overwriting everything again and upgrading to 0.6.1, since it already attempted to upgrade to 0.7.0?

If the suggestion above (setting configured_version) works, you can do the database upgrades without having to downgrade Baikal. I suggest making a backup and trying that first.

[Andrewskiz]

Worked perfectly, thanks!