Unable to edit pages after upgrade to 23.08.1

[topazb]

Attempted Debugging

• I have read the debugging page

Searched GitHub Issues

• I have searched GitHub for the issue.

Describe the Scenario

After upgrading to v23.08.1
I'm unable to edit already existing pages
The edit page appears blank

Exact BookStack Version

23.08.1

Log Content

No response

PHP Version

No response

Hosting Environment

upgraded using the official script

[daviserez]

I'v got a similar issue, but only on some pages and I can't figure out why some pages work and others don't.

Cleared browser cache and app caches.

[cdrfun]

I can +1 to @daviserez issue. Tested it on different machines with up-to-date Firefox, Edge and Chrome. If a page is broken, it is broken on all browser/machines.

[rockenren]

Not all pages are affected, but 2c20abc alone doesn't resolve the issue.

[ssddanbrown]

but 2c20abc alone doesn't resolve the issue.

@rockenren Can you confirm how you tested that? Was just about to push it into release but will hold off if it doesn't address the issue.

[rockenren]

but 2c20abc alone doesn't resolve the issue.

@rockenren Can you confirm how you tested that? Was just about to push it into release but will hold off if it doesn't address the issue.

since this is a small fix: just copied raw from newer revision to current one.
Cleared bookstack caches and restarted web server/php, CTRL+F5 in browser.

Then tried editing broken page again, still showing no content and have same js exception in dev console.

Maybe I did something wrong? Should I pull from development branch via git for this single commit?

[ssddanbrown]

@rockenren JavaScript (and CSS) has to be built/bundled into the expected output file(s). I'm assuming this was not done based upon your response so I went ahead and pushed the release.

Thanks @topazb and everyone else for reporting/confirming the issue.
Should now be addressed in v23.08.2, but please let me know if you continue to have issues and I'll re-open.

[rockenren]

@rockenren JavaScript (and CSS) has to be built/bundled into the expected output file(s). I'm assuming this was not done based upon your response so I went ahead and pushed the release.

Thanks @topazb and everyone else for reporting/confirming the issue. Should now be addressed in v23.08.2, but please let me know if you continue to have issues and I'll re-open.

yes, i've suspected this, my bad.