mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Empty pages are saved as drafts #5342
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @prohtex on GitHub (Jul 2, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
One of the things I love about BookStack is all the little thoughtful touches-everything is where I expect it to be, and there's very little clutter, feature creep, UI crowding, etc. Performance is incredible.
In keeping with this spirit of less-is-more, I noticed a strange behavior recently. When a page is created and not explicitly deleted, the empty page is saved as a draft. The expected behavior would be that an empty page (one with no title or content) is not saved as a draft. Users are backing out of creating new pages (when, for example, they are put in the wrong place) and those blank pages are getting saved, requiring a few extra steps to delete.
I'm wondering if this is normal, or if one of my Javascript injections is putting something in the blank page that's causing it to be saved.
Exact BookStack Version
Latest
Log Content
Hosting Environment
Docker
@ssddanbrown commented on GitHub (Jul 2, 2025):
Hi @prohtex,
Yeah, that's normal.
We really need to have the page created by the time the user reaches the editor to provide as a target for things like uploaded images, attachments etc... otherwise we'd need to have a lot of extra handling involved.
Kinda similar for trying to specifically handle the user backing out, since we'd need to specifically identify and handle such an event.
As an easier option, maybe, while in this initial draft state, we could more prominently feature some kind of "Discard" option (which does exist albeit fairly hidden in the draft menu and currently requires an extra step in the process via its own delete page). I'm not sure if that would just be mostly missed/avoided too though.
@prohtex commented on GitHub (Jul 2, 2025):
What if the "Back" action performs an additional check, and if the title of the page is still "New Page," and the content is empty (including attachments, tags, etc), the draft is deleted?
@ssddanbrown commented on GitHub (Jul 2, 2025):
Yeah, that's another option, but then we get into the extra handling involved to detect that state and to have a specific back route action. All doable, just a bit of extra faff as we would need specific handling. Would want to add specific change title change handling (to avoid checking against each language possibility and to avoid ignoring intended cross-language changes) and check of lack of editor text (not just empty as the editors will send content when empty).
Then there's still the question if that button is actually used or are users actually using browser controls or other navigation buttons/actions.
Either way, I'm going to close this off since the original question has been answered and the fundamental desire/request is already open in #1147.
@prohtex commented on GitHub (Jul 2, 2025):
Thanks for explaining.