Migration error from upgrade 25.7.3 to 25.12.8

[RogerSik]

Attempted Debugging

• I have read the debugging page

Searched GitHub Issues

• I have searched GitHub for the issue.

Describe the Scenario

When upgrading from 25.7.3 to 25.12.8 follow error occurs:

wait-for-db: waiting for bookstack-db-stg.bookstack-stg.svc.cluster.local:3306
wait-for-db: done
Starting Migration...

   INFO  Running migrations.

  2025_09_15_134751_update_entity_relation_columns ............... 5.35ms FAIL

In Connection.php line 838:

  SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP FOREIGN
  KEY `bookshelves_books_book_id_foreign`; check that it exists (Connection:
  mysql, Host: bookstack-db-stg.bookstack-stg.svc.cluster.local, Port: 3306,
  Database: app, SQL: alter table `bookshelves_books` drop foreign key `books
  helves_books_book_id_foreign`)


In Connection.php line 584:

  SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP FOREIGN
  KEY `bookshelves_books_book_id_foreign`; check that it exists

A downgrade to 25.7.3 to is possible. But I'm not sure how to fix these errors to be able to upgrade to 25.12.8

I could partly fix it thanks to #6046

Altered bookshelves_books.book_id bigint into int
Altered bookshelves_books.bookshelf_id bigint into int
Add constraint between bookshelves_books.book_id and books.id
Add constraint between bookshelves_books.bookshelf_id and bookshelves.id

Which is in code

-- Change column types  
ALTER TABLE bookshelves_books  
MODIFY book_id INT UNSIGNED;  
  
ALTER TABLE bookshelves_books  
MODIFY bookshelf_id INT UNSIGNED;  
  
-- Add foreign key constraints  
ALTER TABLE bookshelves_books  
ADD CONSTRAINT bookshelves_books_book_id_foreign  
FOREIGN KEY (book_id) REFERENCES books(id)  
ON DELETE CASCADE;  
  
ALTER TABLE bookshelves_books  
ADD CONSTRAINT bookshelves_books_bookshelf_id_foreign  
FOREIGN KEY (bookshelf_id) REFERENCES bookshelves(id)  
ON DELETE CASCADE;

It fixed that the migration was running successful and bookstack is again accessible. But when accessing / editing of pages I see only older version. A workaround is to get into the Bookstack page revision and restore the newest version.

The Page revisions:

Kindly asking if somehow knows a solution for it. I'm trying digging here and if I find a solution I will post it here.

Exact BookStack Version

25.7.3

Log Content

Hosting Environment

Ubuntu 24.04 with rke2 1.33.5

[ssddanbrown]

Hi @RogerSik,

But when accessing / editing of pages I see only older version.

That's very strange, I really don't understand how old content would end up being used like that.

• Are there any other customisations applied to this instance at all, or have there been any prior manual database changes?
• Has this instance been migrated/restored at any point in the past?

[RogerSik]

Are there any other customisations applied to this instance at all, or have there been any prior manual database changes?

No.

Has this instance been migrated/restored at any point in the past?

No.

Is there a sql query to say that bookstack pages should point to the newest revision / or say restore it to the newest page version?

[RogerSik]

Its looks that the revision page reference was not migrated / is now on another place. I restored id 74 and instead of becoming of 75 it becomes now 57 (and before it was outdated but as last shown 56).

[ssddanbrown]

Both of these things would indicate a mis-match of data during migration, in a way that's unrelated to the original error mentioned during migration.

The revision number shown comes from the entity_page_data.revision_count column in the new database structure, which would have been the pages.revision_count column before.
This data is migrated at this point:

BookStack/database/migrations/2025_09_15_134701_migrate_entity_data.php

Lines 59 to 63 in 4c7d642

	DB::table('entity_page_data')->insertUsing([
	'page_id', 'draft', 'template', 'revision_count', 'editor', 'html', 'text', 'markdown',
	], DB::table('pages')->select([
	'id', 'draft', 'template', 'revision_count', 'editor', 'html', 'text', 'markdown',
	]));

I'm not sure how this could have gone wrong in a way which presents your issues.

• Since your setup mentions a "cluster", is there any chance you had multiple app or multiple database containers running for this setup at one time?
• Does this happen consistently for all pre-existing pages?

[RogerSik]

Oh, sorry forgot to answer your question, but I could fix it. :)

Since your setup mentions a "cluster", is there any chance you had multiple app or multiple database containers running for this setup at one time?

It's running with the Recreate strategy and has a long startup probe to prevent container kill. Multiple container start is not allowed. But I can't guarantee that there was a failed migration and instead of exiting / stopping the container it did a passtrough.

Does this happen consistently for all pre-existing pages?

No not for alle pre-existing pages but for all pages updates / pages creation since about 3 months.

Fix

Stop Bookstack container and start container with sleep

command: ['sh', '-c', 'sleep infinity']

Running SQL Query

DELETE FROM entity_page_data;
DELETE FROM entity_container_data;
DELETE FROM entities WHERE type IN ('book','chapter','page','bookshelf');

DELETE FROM migrations WHERE migration IN (
  '2025_09_15_134701_migrate_entity_data',
  '2025_09_15_134751_update_entity_relation_columns'
);

Remove dropForeing key from database/migrations/2025_09_15_134751_update_entity_relation_columns.php

Manually execute migration

php artisan migrate --path=database/migrations/2025_09_15_134701_migrate_entity_data.php
php artisan migrate --path=database/migrations/2025_09_15_134751_update_entity_relation_columns.php

Start Bookstack container as normally. Wait for all migrations since update. I set container image now to 26.3.2.

Working instance with no outdated / missing pages 🥳

[vladaman]

We have the same issue. Is there any fix without loosing data? We use single instance of Bookstack and now we're stuck with 500 errors after an upgrade. We are in inconsistent state. I had to recover back from backup.

[RogerSik]

@vladaman for me there was no losing data when executing the steps above.