[ Web Proxy ]
URL:
Viewing: https://codeberg.org/bookstack.rss [Back]  [Original]

Feed of "BookStack" https://codeberg.org/bookstack Sat, 29 Aug 2026 02:42:22 +0200 clementvc commented on issue bookstack/bookstack#6199 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> Query results:

]]> clementvc 199900139: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21928643 Fri, 28 Aug 2026 21:05:10 +0200 danb commented on issue bookstack/bookstack#6199 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&#39;s an SQL query to run against your BookStack database:</p> @clementvc Here's an SQL query to run against your BookStack database:

]]> danb 199816997: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21883808 Fri, 28 Aug 2026 17:24:01 +0200 clementvc commented on issue bookstack/bookstack#6199 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> Any thoughts regarding next steps to resolve this issue?

]]> clementvc 199759571: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21878717 Fri, 28 Aug 2026 15:12:17 +0200 danb opened issue bookstack/bookstack#6201 https://codeberg.org/bookstack/bookstack/issues/6201 6201#Verify session for security related changes# Description

Continues from #6181.

Ideally, we'd verify the current user session when making security related changes (User password/role changes).
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).

Some fundamental changes needed to user/session management beforehand though to better track session lifetimes.

]]> danb 199701101: https://codeberg.org/bookstack/bookstack/issues/6201 Fri, 28 Aug 2026 12:49:45 +0200 danb closed issue bookstack/bookstack#6181 https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854792 Verify existing password for user password changes danb 199698395: https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854792 Fri, 28 Aug 2026 12:46:14 +0200 danb commented on issue bookstack/bookstack#6181 https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854789 Verify existing password for user password changes <p dir="auto">Added within 7539933d48c824b641a744c5b22d63a48e6d8cc3.</p> Added within 7539933d48c824b641a744c5b22d63a48e6d8cc3.

]]> danb 199698335: https://codeberg.org/bookstack/bookstack/issues/6181#issuecomment-21854789 Fri, 28 Aug 2026 12:46:14 +0200 danb pushed to development at bookstack/bookstack https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3 <a href="https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3">7539933d48c824b641a744c5b22d63a48e6d8cc3</a> User Account: Require existing password on password change 7539933d48c824b641a744c5b22d63a48e6d8cc3 User Account: Require existing password on password change]]> danb 199697183: https://codeberg.org/bookstack/bookstack/commit/7539933d48c824b641a744c5b22d63a48e6d8cc3 Fri, 28 Aug 2026 12:43:16 +0200 danb closed issue bookstack/bookstack#6162 https://codeberg.org/bookstack/bookstack/issues/6162#issuecomment-21853529 API: Provide Changelog on Page Update danb 199679567: https://codeberg.org/bookstack/bookstack/issues/6162#issuecomment-21853529 Fri, 28 Aug 2026 11:58:06 +0200 danb commented on issue bookstack/bookstack#6162 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> This has now been added via 4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1, and will be part of the next feature release.

]]> danb 199679507: https://codeberg.org/bookstack/bookstack/issues/6162#issuecomment-21853526 Fri, 28 Aug 2026 11:58:06 +0200 danb pushed to development at bookstack/bookstack https://codeberg.org/bookstack/bookstack/compare/c70b2991948d1547470f3d6afd62fd64ea522f75...4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1 <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 4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1 API: Added changelog support to page create/update API f1fe98d1946bd8dba92e760880db85280eb71f86 Pages API: Added extra test to cover type mismatch scenario]]> danb 199678961: https://codeberg.org/bookstack/bookstack/compare/c70b2991948d1547470f3d6afd62fd64ea522f75...4a871811e9dad41175a7ddd907ecb4ef4f5fe8b1 Fri, 28 Aug 2026 11:57:31 +0200 danb commented on pull request bookstack/bookstack#6165 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> Hi @magordon,

]]> danb 199242146: https://codeberg.org/bookstack/bookstack/pulls/6165#issuecomment-21817442 Thu, 27 Aug 2026 17:07:17 +0200 noviceuser opened issue bookstack/bookstack#6200 https://codeberg.org/bookstack/bookstack/issues/6200 6200#BookStack FORMS# Describe the feature you'd like

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).
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.

Describe the benefits this would bring to existing BookStack users

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.
Super basic.
Provide a line at the bottom for them to sign and boom... form/compliance/whatever you want to call it, done.

Uses could be:

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.

Can the goal of this request already be achieved via other means?

Not that I am aware.

Have you searched for an existing open/closed issue?

How long have you been using BookStack?

1 to 5 years

Additional context

No response

Have you used generative AI/LLMs to create any thoughts in this request?

]]> noviceuser 199231520: https://codeberg.org/bookstack/bookstack/issues/6200 Thu, 27 Aug 2026 16:40:52 +0200 noviceuser commented on issue bookstack/bookstack#6197 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&#39;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 &#34;John Doe&#34; 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 &#34;Frank Murray&#34; 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&#39;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&#39;t that because this is self contained. Similar to anchor links in a ToC.</p> 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:

I should be able to have a place that in the document I can say: (@1)John Doe(1@) was found roaming around 8th Avenue by (@2)Detective Gonzalez(2@)....

Then later in the same article anywhere I want "John Doe" I could just use {@1} and it would replace that with John Doe.

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.

It is not a global variable, it isn't a universal variable (like time), and while I do seriously like #4610, this also isn't that because this is self contained. Similar to anchor links in a ToC.

]]> noviceuser 199228521: https://codeberg.org/bookstack/bookstack/issues/6197#issuecomment-21816032 Thu, 27 Aug 2026 16:32:46 +0200 danb closed issue bookstack/bookstack#6136 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} danb 199223003: https://codeberg.org/bookstack/bookstack/issues/6136#issuecomment-21815459 Thu, 27 Aug 2026 16:21:35 +0200 danb commented on issue bookstack/bookstack#6136 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> Thanks @nathandg for raising, and thanks @WhyNotFlipFlop for confirming.

]]> danb 199222940: https://codeberg.org/bookstack/bookstack/issues/6136#issuecomment-21815456 Thu, 27 Aug 2026 16:21:35 +0200 clementvc commented on issue bookstack/bookstack#6199 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> We have no modifications other than adding a logo, app icon, and changing the colors.

]]> clementvc 199222658: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21815417 Thu, 27 Aug 2026 16:21:06 +0200 noahdoersing commented on issue bookstack/bookstack#3103 https://codeberg.org/bookstack/bookstack/issues/3103#issuecomment-21810326 [API Request]: Page Revisions Endpoint <p dir="auto">Because this isn&#39;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> Because this isn't explicitly stated in the original issue: Including the content of each revision would also be great, enabling tracking of what exactly changed (using external tooling) and not just when it did so.

]]> noahdoersing 199158399: https://codeberg.org/bookstack/bookstack/issues/3103#issuecomment-21810326 Thu, 27 Aug 2026 14:15:08 +0200 danb commented on issue bookstack/bookstack#473 https://codeberg.org/bookstack/bookstack/issues/473#issuecomment-21807920 [FEATURE REQUEST] Status / Review Workflow <blockquote> <p dir="auto">Hence, why not assign it the &#34;next next future release&#34; milestone?</p> </blockquote>

Hence, why not assign it the "next next future release" milestone?

]]> danb 199129325: https://codeberg.org/bookstack/bookstack/issues/473#issuecomment-21807920 Thu, 27 Aug 2026 13:08:45 +0200 TeeLittle commented on issue bookstack/bookstack#473 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 &#34;works for me&#34;. So I assume you acknowledge the fundamental significance of a wiki being able to distinguish &#34;released&#34; status from &#34;draft&#34;.<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 &#34;next next future release&#34; 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 &#34;release&#34; workflow.<br/> (additionally, such a perspective would keep people from putting effort into crafting all kind of workarounds...)</p> 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".
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.
Summarising, both the developer and the community agree on the importance of some kind of release workflow.
Hence, why not assign it the "next next future release" milestone?
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.
(additionally, such a perspective would keep people from putting effort into crafting all kind of workarounds...)

]]> TeeLittle 199105097: https://codeberg.org/bookstack/bookstack/issues/473#issuecomment-21804458 Thu, 27 Aug 2026 12:09:30 +0200 danb closed issue bookstack/bookstack#6089 https://codeberg.org/bookstack/bookstack/issues/6089#issuecomment-21794891 PHPStan Level 5 danb 199098828: https://codeberg.org/bookstack/bookstack/issues/6089#issuecomment-21794891 Thu, 27 Aug 2026 11:55:22 +0200 danb commented on issue bookstack/bookstack#6089 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> Merged via #6143

]]> danb 199098765: https://codeberg.org/bookstack/bookstack/issues/6089#issuecomment-21794885 Thu, 27 Aug 2026 11:55:21 +0200 danb closed issue bookstack/bookstack#1145 https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785372 Reflect the page revision that a comment relates to danb 199082504: https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785372 Thu, 27 Aug 2026 11:18:56 +0200 danb commented on issue bookstack/bookstack#1145 https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785369 Reflect the page revision that a comment relates to <p dir="auto">Since there&#39;s been no further request for this I&#39;m going to go ahead and close off this issue.</p> Since there's been no further request for this I'm going to go ahead and close off this issue.

]]> danb 199082441: https://codeberg.org/bookstack/bookstack/issues/1145#issuecomment-21785369 Thu, 27 Aug 2026 11:18:55 +0200 danb closed issue bookstack/bookstack#6191 https://codeberg.org/bookstack/bookstack/issues/6191#issuecomment-21767009 Provide a way to download API docs in a machine readable file danb 198750201: https://codeberg.org/bookstack/bookstack/issues/6191#issuecomment-21767009 Thu, 27 Aug 2026 00:04:23 +0200 danb commented on issue bookstack/bookstack#6191 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> Closed via #6198

]]> danb 198750135: https://codeberg.org/bookstack/bookstack/issues/6191#issuecomment-21767003 Thu, 27 Aug 2026 00:04:22 +0200 danb deleted branch api_docs_download from bookstack/bookstack https://codeberg.org/bookstack/bookstack danb 198749849: https://codeberg.org/bookstack/bookstack Thu, 27 Aug 2026 00:04:08 +0200 danb merged pull request bookstack/bookstack#6198 https://codeberg.org/bookstack/bookstack/pulls/6198 API Docs: Added new endpoints to download docs as html/json danb 198749784: https://codeberg.org/bookstack/bookstack/pulls/6198 Thu, 27 Aug 2026 00:04:06 +0200 danb pushed to development at bookstack/bookstack https://codeberg.org/bookstack/bookstack/compare/fac26126d5717aa7c5659fc6180a37085e0d1282...c70b2991948d1547470f3d6afd62fd64ea522f75 <a href="https://codeberg.org/bookstack/bookstack/commit/c70b2991948d1547470f3d6afd62fd64ea522f75">c70b2991948d1547470f3d6afd62fd64ea522f75</a> Merge pull request &#39;API Docs: Added new endpoints to download docs as html/json&#39; (#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 c70b2991948d1547470f3d6afd62fd64ea522f75 Merge pull request 'API Docs: Added new endpoints to download docs as html/json' (#6198) from api_docs_download into development 8603266f7728203fd90eb3a21b76a2fd57e7f816 API Docs: Covered download endpoints with tests 35b6f57912cfbc56e4b875b9f41b568aedf5cd71 API Docs: Added new endpoints to download docs as html/json]]> danb 198749664: https://codeberg.org/bookstack/bookstack/compare/fac26126d5717aa7c5659fc6180a37085e0d1282...c70b2991948d1547470f3d6afd62fd64ea522f75 Thu, 27 Aug 2026 00:04:03 +0200 danb commented on issue bookstack/bookstack#6199 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> Thanks for confirming @clementvc.

]]> danb 198734528: https://codeberg.org/bookstack/bookstack/issues/6199#issuecomment-21766043 Wed, 26 Aug 2026 23:36:52 +0200 danb pushed to api_docs_download at bookstack/bookstack https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816 <a href="https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816">8603266f7728203fd90eb3a21b76a2fd57e7f816</a> API Docs: Covered download endpoints with tests 8603266f7728203fd90eb3a21b76a2fd57e7f816 API Docs: Covered download endpoints with tests]]> danb 198732206: https://codeberg.org/bookstack/bookstack/commit/8603266f7728203fd90eb3a21b76a2fd57e7f816 Wed, 26 Aug 2026 23:30:29 +0200
Web Proxy Viewer  |  New URL  |  Original Page