Updated from 0.17.4 to 0.18.0, cannot open books #428

New Issue

OVERLORD · 2026-02-04T19:55:36+03:00

OVERLORD commented

2026-02-04 19:55:36 +03:00

Originally created by @m4ntic0r on GitHub (Sep 11, 2017).

Updated from 0.17.4 to 0.18.0, cannot open books

i can login, but if i click on a book i get only "Whoops, looks like something went wrong."

i had this problem before, its a bit annoying after every update.
https://github.com/BookStackApp/BookStack/issues/287

laravel.log:
https://pastebin.com/QRQmMdrh

Originally created by @m4ntic0r on GitHub (Sep 11, 2017). Updated from 0.17.4 to 0.18.0, cannot open books i can login, but if i click on a book i get only "Whoops, looks like something went wrong." i had this problem before, its a bit annoying after every update. https://github.com/BookStackApp/BookStack/issues/287 laravel.log: https://pastebin.com/QRQmMdrh

OVERLORD added the 🐕 Support label 2026-02-04 19:55:36 +03:00

OVERLORD closed this issue

2026-02-04 19:55:46 +03:00

OVERLORD commented

2026-02-04 19:55:52 +03:00

@ssddanbrown commented on GitHub (Sep 11, 2017):

Hi @m4ntic0r, Sorry to hear you're having issues with the update.

This appears to be a different issue compare to your previous upgrade woes.

Could you confirm your PHP & MySQL versions?
Also, Just confirm if the upgrade commands ran smoothly and if running git status from your BookStack install folder gives any output.

@ssddanbrown commented on GitHub (Sep 11, 2017): Hi @m4ntic0r, Sorry to hear you're having issues with the update. This appears to be a different issue compare to your previous upgrade woes. Could you confirm your PHP & MySQL versions? Also, Just confirm if the upgrade commands ran smoothly and if running `git status` from your BookStack install folder gives any output.

OVERLORD commented

2026-02-04 19:56:02 +03:00

@m4ntic0r commented on GitHub (Sep 11, 2017):

php: Version: 7.0.22-0ubuntu0.17.04.1
mysql: Version: 5.7.19-0ubuntu0.17.04.1

I have no explanation for this, but i restored my failed upgrade to previous working version via vmware snapshot and mysql backup and run the update with the same command again. now it works without any problems.

@m4ntic0r commented on GitHub (Sep 11, 2017): php: Version: 7.0.22-0ubuntu0.17.04.1 mysql: Version: 5.7.19-0ubuntu0.17.04.1 I have no explanation for this, but i restored my failed upgrade to previous working version via vmware snapshot and mysql backup and run the update with the same command again. now it works without any problems.

OVERLORD commented

2026-02-04 19:56:13 +03:00

@ghost commented on GitHub (Sep 18, 2017):

It sounds like you didn't get the comments column in your database.

I had the same issue where it got flubbed in the composer install and didn't complete the php artisan migrate. When I ran sudo php artisan migrate it completed updating the comment column.

@ghost commented on GitHub (Sep 18, 2017): It sounds like you didn't get the comments column in your database. I had the same issue where it got flubbed in the composer install and didn't complete the php artisan migrate. When I ran sudo php artisan migrate it completed updating the comment column.

OVERLORD commented

2026-02-04 19:56:26 +03:00

@ssddanbrown commented on GitHub (Sep 23, 2017):

Glad to hear this is now resolved, Will close this issue.

@ssddanbrown commented on GitHub (Sep 23, 2017): Glad to hear this is now resolved, Will close this issue.

OVERLORD referenced this issue

2026-02-04 20:32:38 +03:00

Feature Request: Pop up notes #489

Sign in to join this conversation.