mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-05-04 18:08:46 +03:00
Book, Chapter, Page URL by using id instead of permalink #5300
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 @nexgen on GitHub (May 29, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
Is there anyway I can construct a url by id only instead of using slug/permalink?
Exact BookStack Version
latest
Log Content
No response
Hosting Environment
ubuntu
@ssddanbrown commented on GitHub (May 30, 2025):
Hi @nexgen,
We provide an id-based URL for pages.
This can be accessed via the popover when you select some page text:
This link will be a redirect though to the (slug-based) page URL, and we don't provide such a mechanism for books/chapters.
@nexgen commented on GitHub (May 30, 2025):
I'm syncing some notes offline and for now I'm creating the link using the slug. However, whenever I rename the book/chapter/page the slug gets modified which breaks the link I have stored. It would be great to have alternative link like:
http://bookstack.com/?book=12
http://bookstack.com/?chatper=15
http://bookstack.com/?page=19
etc...
Where 12, 15, 19 or the ids of book/chapter/page
@Ionys320 commented on GitHub (May 30, 2025):
I would suggest a system with title + id in the URL, with the following format:
https://example.com/hello-world-123bf79.The advantage is that you use the id only to determine which ressource it belongs to.
Therefore, both
https://example.com/hello-world-123bf79andhttps://example.com/my-cat-is-awesome-123bf79would work without any redirection stuff, only by using123bf79as the ID.@nexgen commented on GitHub (May 31, 2025):
it still doesn't solve my problem. Those are not valid links for bookstack.
@ssddanbrown commented on GitHub (May 31, 2025):
I'm going to close this off since the original question in this support thread was answered, and since there's an existing request for similar permalinks for other content types open in #1781.
@Ionys320 I was thinking of a similar hybrid like that in my proposal in #3520, but ultimately changing URL scheme or even just adding support for another is not really something I'd deem worthwhile as per my thoughts in that thread.