Feed of "BookStack"
https://codeberg.org/bookstack
2026-08-29T16:11:17+02:00
clementvc commented on issue bookstack/bookstack#6199
2026-08-28T21:05:10+02:00
199900139: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21928643
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Query results:</p>
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Query results:</p>
clementvc
clementvc@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6199
2026-08-28T17:24:01+02:00
199816997: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21883808
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto"><a href="/clementvc" class="mention" rel="nofollow">@clementvc</a> Here's an SQL query to run against your BookStack database:</p>
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto"><a href="/clementvc" class="mention" rel="nofollow">@clementvc</a> Here's an SQL query to run against your BookStack database:</p>
danb
danb@noreply.codeberg.org
clementvc commented on issue bookstack/bookstack#6199
2026-08-28T15:12:17+02:00
199759571: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21878717
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Any thoughts regarding next steps to resolve this issue?</p>
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Any thoughts regarding next steps to resolve this issue?</p>
clementvc
clementvc@noreply.codeberg.org
danb opened issue bookstack/bookstack#6201
2026-08-28T12:49:45+02:00
199701101: https://codeberg.org/bookstack/bookstack/issues/6201
<h3 id="user-content-description" dir="auto">Description</h3>
<p dir="auto">Continues from <a href="/bookstack/bookstack/issues/6181" class="ref-issue" rel="nofollow">#6181</a>.</p>
<p dir="auto">Ideally, we'd verify the current user session when making security related changes (User password/role changes).<br/>
Essentially have a more restricted session lifetime control for these elements to help prevent scenarios where the user session may be hijacked (stolen token, unlocked PC).</p>
<p dir="auto">Some fundamental changes needed to user/session management beforehand though to better track session lifetimes.</p>
6201#Verify session for security related changes#
danb
danb@noreply.codeberg.org
danb closed issue bookstack/bookstack#6181
2026-08-28T12:46:14+02:00
199698395: https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854792
Verify existing password for user password changes
Verify existing password for user password changes
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6181
2026-08-28T12:46:14+02:00
199698335: https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854789
Verify existing password for user password changes
<p dir="auto">Added within 7539933d48c824b641a744c5b22d63a48e6d8cc3.</p>
Verify existing password for user password changes
<p dir="auto">Added within 7539933d48c824b641a744c5b22d63a48e6d8cc3.</p>
danb
danb@noreply.codeberg.org
danb pushed to development at bookstack/bookstack
2026-08-28T12:43:16+02:00
199697183: https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3
<a href="https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3" rel="nofollow">7539933d48c824b641a744c5b22d63a48e6d8cc3</a>
User Account: Require existing password on password change
<a href="https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3">7539933d48c824b641a744c5b22d63a48e6d8cc3</a>
User Account: Require existing password on password change
danb
danb@noreply.codeberg.org
danb closed issue bookstack/bookstack#6162
2026-08-28T11:58:06+02:00
199679567: https://codeberg.org/bookstack/bookstack/issues/6162#issuecomment-21853529
API: Provide Changelog on Page Update
API: Provide Changelog on Page Update
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6162
2026-08-28T11:58:06+02:00
199679507: https://codeberg.org/bookstack/bookstack/issues/6162#issuecomment-21853526
API: Provide Changelog on Page Update
<p dir="auto">This has now been added via 4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1, and will be part of the next feature release.</p>
API: Provide Changelog on Page Update
<p dir="auto">This has now been added via 4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1, and will be part of the next feature release.</p>
danb
danb@noreply.codeberg.org
danb pushed to development at bookstack/bookstack
2026-08-28T11:57:31+02:00
199678961: https://codeberg.org/bookstack/bookstack/compare/c70b2991948d1547470f3d6afd62fd64ea522f75...4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1
<a href="https://codeberg.org/bookstack/bookstack/commit/4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1" rel="nofollow">4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1</a>
API: Added changelog support to page create/update API
<a href="https://codeberg.org/bookstack/bookstack/commit/f1fe98d1946bd8dba92e760880db85280eb71f86" rel="nofollow">f1fe98d1946bd8dba92e760880db85280eb71f86</a>
Pages API: Added extra test to cover type mismatch scenario
<a href="https://codeberg.org/bookstack/bookstack/commit/4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1">4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1</a>
API: Added changelog support to page create/update API
<a href="https://codeberg.org/bookstack/bookstack/commit/f1fe98d1946bd8dba92e760880db85280eb71f86">f1fe98d1946bd8dba92e760880db85280eb71f86</a>
Pages API: Added extra test to cover type mismatch scenario
danb
danb@noreply.codeberg.org
danb commented on pull request bookstack/bookstack#6165
2026-08-27T17:07:17+02:00
199242146: https://codeberg.org/bookstack/bookstack/pulls/6165#issuecomment-21817442
Update resources/views/layouts/parts/header-logo.blade.php for accessibility issue
<p dir="auto">Hi <a href="/magordon" class="mention" rel="nofollow">@magordon</a>,</p>
Update resources/views/layouts/parts/header-logo.blade.php for accessibility issue
<p dir="auto">Hi <a href="/magordon" class="mention" rel="nofollow">@magordon</a>,</p>
danb
danb@noreply.codeberg.org
noviceuser opened issue bookstack/bookstack#6200
2026-08-27T16:40:52+02:00
199231520: https://codeberg.org/bookstack/bookstack/issues/6200
<h3 id="user-content-describe-the-feature-you-d-like" dir="auto">Describe the feature you'd like</h3>
<p dir="auto">I believe it would be awesome if you could have a way to create fillable forms. Be able to create fields while you are writing, have them be related to also. This way if you have a "Name" field at the top, you can just reuse the information from that field in any other "Name" instances in the document. Heck it would be awesome also if you could tie it into the user's name from the account (or prompt for the option for that).<br/>
I'm not looking to be able to do anything but provide a way for someone to fill a form and then either print it, or export a filled pdf version (right now with the way tables get screwed up, I would say PDF later until that part doesn't happen). No need for email connection etc. just a way to fill a form and print it out.</p>
<h3 id="user-content-describe-the-benefits-this-would-bring-to-existing-bookstack-users" dir="auto">Describe the benefits this would bring to existing BookStack users</h3>
<p dir="auto">Expand the platform for those that use it in an SMB situation or really many other things. Create a form, and users can pull it up, fill it out, and print it.<br/>
Super basic.<br/>
Provide a line at the bottom for them to sign and boom... form/compliance/whatever you want to call it, done.</p>
<p dir="auto">Uses could be:</p>
<ul dir="auto">
<li>Tests</li>
<li>Forms</li>
<li>Certificates</li>
</ul>
<p dir="auto">Really anywhere that something can be personalized it will look more professionally done as well as easier to read as you are not trying to read possible bad handwriting.</p>
<h3 id="user-content-can-the-goal-of-this-request-already-be-achieved-via-other-means" dir="auto">Can the goal of this request already be achieved via other means?</h3>
<p dir="auto">Not that I am aware.</p>
<h3 id="user-content-have-you-searched-for-an-existing-open-closed-issue" dir="auto">Have you searched for an existing open/closed issue?</h3>
<ul dir="auto">
<li class="task-list-item"><input type="checkbox" disabled="" data-source-position="1524" checked=""/>I have searched for existing issues and none cover my fundamental request</li>
</ul>
<h3 id="user-content-how-long-have-you-been-using-bookstack" dir="auto">How long have you been using BookStack?</h3>
<p dir="auto">1 to 5 years</p>
<h3 id="user-content-additional-context" dir="auto">Additional context</h3>
<p dir="auto"><em>No response</em></p>
<h3 id="user-content-have-you-used-generative-ai-llms-to-create-any-thoughts-in-this-request" dir="auto">Have you used generative AI/LLMs to create any thoughts in this request?</h3>
<ul dir="auto">
<li class="task-list-item"><input type="checkbox" disabled="" data-source-position="1781" checked=""/>This request only contains the thoughts & ideas of a human</li>
</ul>
6200#BookStack FORMS#
noviceuser
noviceuser@noreply.codeberg.org
noviceuser commented on issue bookstack/bookstack#6197
2026-08-27T16:32:46+02:00
199228521: https://codeberg.org/bookstack/bookstack/issues/6197#issuecomment-21816032
Define variables within a document for reuse in templates
<p dir="auto">I understand why you would want to add it to the other but I am not referring to something to be pulled from an exterior source. I do feel like that should be able to be done as well for the sake of repetitiveness however I am saying if I am writing something, let's say a news article. I have a few players in the article:</p>
<ul dir="auto">
<li>Main1: John Doe</li>
<li>Main2: Detective Gonzalez</li>
</ul>
<p dir="auto">I should be able to have a place that in the document I can say: (<a href="/1" class="mention" rel="nofollow">@1</a>)John Doe(1@) was found roaming around 8th Avenue by (<a href="/2" class="mention" rel="nofollow">@2</a>)Detective Gonzalez(2@)....</p>
<p dir="auto">Then later in the same article anywhere I want "John Doe" I could just use {@1} and it would replace that with John Doe.</p>
<p dir="auto">It would be useful if also information changes and instead of John Doe it is later updated to be "Frank Murray" well I can go into the article and change the top and it changes all instances.</p>
<p dir="auto">It is not a global variable, it isn't a universal variable (like time), and while I do seriously like <a href="/bookstack/bookstack/issues/4610" class="ref-issue" rel="nofollow">#4610</a>, this also isn't that because this is self contained. Similar to anchor links in a ToC.</p>
Define variables within a document for reuse in templates
<p dir="auto">I understand why you would want to add it to the other but I am not referring to something to be pulled from an exterior source. I do feel like that should be able to be done as well for the sake of repetitiveness however I am saying if I am writing something, let's say a news article. I have a few players in the article:</p>
<ul dir="auto">
<li>Main1: John Doe</li>
<li>Main2: Detective Gonzalez</li>
</ul>
<p dir="auto">I should be able to have a place that in the document I can say: (<a href="/1" class="mention" rel="nofollow">@1</a>)John Doe(1@) was found roaming around 8th Avenue by (<a href="/2" class="mention" rel="nofollow">@2</a>)Detective Gonzalez(2@)....</p>
<p dir="auto">Then later in the same article anywhere I want "John Doe" I could just use {@1} and it would replace that with John Doe.</p>
<p dir="auto">It would be useful if also information changes and instead of John Doe it is later updated to be "Frank Murray" well I can go into the article and change the top and it changes all instances.</p>
<p dir="auto">It is not a global variable, it isn't a universal variable (like time), and while I do seriously like <a href="/bookstack/bookstack/issues/4610" class="ref-issue" rel="nofollow">#4610</a>, this also isn't that because this is self contained. Similar to anchor links in a ToC.</p>
noviceuser
noviceuser@noreply.codeberg.org
danb closed issue bookstack/bookstack#6136
2026-08-27T16:21:35+02:00
199223003: https://codeberg.org/bookstack/bookstack/issues/6136#issuecomment-21815459
API returns 500 Internal Server Error with internal path disclosure when non-numeric ID is passed to /api/pages/{id}
API returns 500 Internal Server Error with internal path disclosure when non-numeric ID is passed to /api/pages/{id}
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6136
2026-08-27T16:21:35+02:00
199222940: https://codeberg.org/bookstack/bookstack/issues/6136#issuecomment-21815456
API returns 500 Internal Server Error with internal path disclosure when non-numeric ID is passed to /api/pages/{id}
<p dir="auto">Thanks <a href="/nathandg" class="mention" rel="nofollow">@nathandg</a> for raising, and thanks <a href="/WhyNotFlipFlop" class="mention" rel="nofollow">@WhyNotFlipFlop</a> for confirming.</p>
API returns 500 Internal Server Error with internal path disclosure when non-numeric ID is passed to /api/pages/{id}
<p dir="auto">Thanks <a href="/nathandg" class="mention" rel="nofollow">@nathandg</a> for raising, and thanks <a href="/WhyNotFlipFlop" class="mention" rel="nofollow">@WhyNotFlipFlop</a> for confirming.</p>
danb
danb@noreply.codeberg.org
clementvc commented on issue bookstack/bookstack#6199
2026-08-27T16:21:06+02:00
199222658: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21815417
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">We have no modifications other than adding a logo, app icon, and changing the colors.</p>
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">We have no modifications other than adding a logo, app icon, and changing the colors.</p>
clementvc
clementvc@noreply.codeberg.org
noahdoersing commented on issue bookstack/bookstack#3103
2026-08-27T14:15:08+02:00
199158399: https://codeberg.org/bookstack/bookstack/issues/3103#issuecomment-21810326
[API Request]: Page Revisions Endpoint
<p dir="auto">Because this isn't explicitly stated in the original issue: Including the <em>content</em> of each revision would also be great, enabling tracking of <em>what</em> exactly changed (using external tooling) and not just <em>when</em> it did so.</p>
[API Request]: Page Revisions Endpoint
<p dir="auto">Because this isn't explicitly stated in the original issue: Including the <em>content</em> of each revision would also be great, enabling tracking of <em>what</em> exactly changed (using external tooling) and not just <em>when</em> it did so.</p>
noahdoersing
noahdoersing@noreply.codeberg.org
danb commented on issue bookstack/bookstack#473
2026-08-27T13:08:45+02:00
199129325: https://codeberg.org/bookstack/bookstack/issues/473#issuecomment-21807920
[FEATURE REQUEST] Status / Review Workflow
<blockquote>
<p dir="auto">Hence, why not assign it the "next next future release" milestone?</p>
</blockquote>
[FEATURE REQUEST] Status / Review Workflow
<blockquote>
<p dir="auto">Hence, why not assign it the "next next future release" milestone?</p>
</blockquote>
danb
danb@noreply.codeberg.org
TeeLittle commented on issue bookstack/bookstack#473
2026-08-27T12:09:30+02:00
199105097: https://codeberg.org/bookstack/bookstack/issues/473#issuecomment-21804458
[FEATURE REQUEST] Status / Review Workflow
<p dir="auto">Reading through this issue, I notice @ssddanbrown has referenced this in quite some similar issues and declined to close it as "works for me". So I assume you acknowledge the fundamental significance of a wiki being able to distinguish "released" status from "draft".<br/>
Browsing and analysing the issue backlog, I see this one here is one of the longest-existing, continuously commented issues with 100+ upvotes on the original issue description, and 160+ upvotes on dozens of comments over nine years.<br/>
Summarising, both the developer and the community agree on the importance of some kind of release workflow.<br/>
Hence, why not assign it the "next next future release" milestone?<br/>
This would leave room for the current editor refining and API amendments works, while providing a clear perspective for those in (organisational) need for a "release" workflow.<br/>
(additionally, such a perspective would keep people from putting effort into crafting all kind of workarounds...)</p>
[FEATURE REQUEST] Status / Review Workflow
<p dir="auto">Reading through this issue, I notice @ssddanbrown has referenced this in quite some similar issues and declined to close it as "works for me". So I assume you acknowledge the fundamental significance of a wiki being able to distinguish "released" status from "draft".<br/>
Browsing and analysing the issue backlog, I see this one here is one of the longest-existing, continuously commented issues with 100+ upvotes on the original issue description, and 160+ upvotes on dozens of comments over nine years.<br/>
Summarising, both the developer and the community agree on the importance of some kind of release workflow.<br/>
Hence, why not assign it the "next next future release" milestone?<br/>
This would leave room for the current editor refining and API amendments works, while providing a clear perspective for those in (organisational) need for a "release" workflow.<br/>
(additionally, such a perspective would keep people from putting effort into crafting all kind of workarounds...)</p>
TeeLittle
teelittle@noreply.codeberg.org
danb closed issue bookstack/bookstack#6089
2026-08-27T11:55:22+02:00
199098828: https://codeberg.org/bookstack/bookstack/issues/6089#issuecomment-21794891
PHPStan Level 5
PHPStan Level 5
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6089
2026-08-27T11:55:21+02:00
199098765: https://codeberg.org/bookstack/bookstack/issues/6089#issuecomment-21794885
PHPStan Level 5
<p dir="auto">Merged via <a href="/bookstack/bookstack/issues/6143" class="ref-issue" rel="nofollow">#6143</a></p>
PHPStan Level 5
<p dir="auto">Merged via <a href="/bookstack/bookstack/issues/6143" class="ref-issue" rel="nofollow">#6143</a></p>
danb
danb@noreply.codeberg.org
danb closed issue bookstack/bookstack#1145
2026-08-27T11:18:56+02:00
199082504: https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785372
Reflect the page revision that a comment relates to
Reflect the page revision that a comment relates to
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#1145
2026-08-27T11:18:55+02:00
199082441: https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785369
Reflect the page revision that a comment relates to
<p dir="auto">Since there's been no further request for this I'm going to go ahead and close off this issue.</p>
Reflect the page revision that a comment relates to
<p dir="auto">Since there's been no further request for this I'm going to go ahead and close off this issue.</p>
danb
danb@noreply.codeberg.org
danb closed issue bookstack/bookstack#6191
2026-08-27T00:04:23+02:00
198750201: https://codeberg.org/bookstack/bookstack/issues/6191#issuecomment-21767009
Provide a way to download API docs in a machine readable file
Provide a way to download API docs in a machine readable file
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6191
2026-08-27T00:04:22+02:00
198750135: https://codeberg.org/bookstack/bookstack/issues/6191#issuecomment-21767003
Provide a way to download API docs in a machine readable file
<p dir="auto">Closed via <a href="/bookstack/bookstack/issues/6198" class="ref-issue" rel="nofollow">#6198</a></p>
Provide a way to download API docs in a machine readable file
<p dir="auto">Closed via <a href="/bookstack/bookstack/issues/6198" class="ref-issue" rel="nofollow">#6198</a></p>
danb
danb@noreply.codeberg.org
danb deleted branch api_docs_download from bookstack/bookstack
2026-08-27T00:04:08+02:00
198749849: https://codeberg.org/bookstack/bookstack
danb
danb@noreply.codeberg.org
danb merged pull request bookstack/bookstack#6198
2026-08-27T00:04:06+02:00
198749784: https://codeberg.org/bookstack/bookstack/pulls/6198
API Docs: Added new endpoints to download docs as html/json
API Docs: Added new endpoints to download docs as html/json
danb
danb@noreply.codeberg.org
danb pushed to development at bookstack/bookstack
2026-08-27T00:04:03+02:00
198749664: https://codeberg.org/bookstack/bookstack/compare/fac26126d5717aa7c5659fc6180a37085e0d1282...c70b2991948d1547470f3d6afd62fd64ea522f75
<a href="https://codeberg.org/bookstack/bookstack/commit/c70b2991948d1547470f3d6afd62fd64ea522f75" rel="nofollow">c70b2991948d1547470f3d6afd62fd64ea522f75</a>
Merge pull request 'API Docs: Added new endpoints to download docs as html/json' (#6198) from api_docs_download into development
<a href="https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816" rel="nofollow">8603266f7728203fd90eb3a21b76a2fd57e7f816</a>
API Docs: Covered download endpoints with tests
<a href="https://codeberg.org/bookstack/bookstack/commit/35b6f57912cfbc56e4b875b9f41b568aedf5cd71" rel="nofollow">35b6f57912cfbc56e4b875b9f41b568aedf5cd71</a>
API Docs: Added new endpoints to download docs as html/json
<a href="https://codeberg.org/bookstack/bookstack/commit/c70b2991948d1547470f3d6afd62fd64ea522f75">c70b2991948d1547470f3d6afd62fd64ea522f75</a>
Merge pull request 'API Docs: Added new endpoints to download docs as html/json' (#6198) from api_docs_download into development
<a href="https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816">8603266f7728203fd90eb3a21b76a2fd57e7f816</a>
API Docs: Covered download endpoints with tests
<a href="https://codeberg.org/bookstack/bookstack/commit/35b6f57912cfbc56e4b875b9f41b568aedf5cd71">35b6f57912cfbc56e4b875b9f41b568aedf5cd71</a>
API Docs: Added new endpoints to download docs as html/json
danb
danb@noreply.codeberg.org
danb commented on issue bookstack/bookstack#6199
2026-08-26T23:36:52+02:00
198734528: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21766043
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Thanks for confirming <a href="/clementvc" class="mention" rel="nofollow">@clementvc</a>.</p>
Error creating new page after upgrading to BookStack v26.05.4
<p dir="auto">Thanks for confirming <a href="/clementvc" class="mention" rel="nofollow">@clementvc</a>.</p>
danb
danb@noreply.codeberg.org
danb pushed to api_docs_download at bookstack/bookstack
2026-08-26T23:30:29+02:00
198732206: https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816
<a href="https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816" rel="nofollow">8603266f7728203fd90eb3a21b76a2fd57e7f816</a>
API Docs: Covered download endpoints with tests
<a href="https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816">8603266f7728203fd90eb3a21b76a2fd57e7f816</a>
API Docs: Covered download endpoints with tests
danb
danb@noreply.codeberg.org