mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 00:59:39 +03:00
Code instead of wiki pages #5294
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 @Jens-TGS on GitHub (May 26, 2025).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I already did several updates of my nice bookstack installation, but this time when updating to 25.02.5 things went wrong. If I now open my wiki URL, I'm getting redirected to
https://wiki.my-domain.com/login
and this page looks like this:
`@extends('layouts.simple') @section('content')
{{ Str::title(trans('auth.log_in')) }}
@include('auth.parts.login-message') @include('auth.parts.login-form-' . $authMethod) @if(count($socialDrivers) > 0) @foreach($socialDrivers as $driver => $name)
@icon('auth/' . $driver) {{ trans('auth.log_in_with', ['socialDriver' => $name]) }}
@endforeach @endif @if(setting('registration-enabled') && config('auth.method') === 'standard')
{{ trans('auth.dont_have_account') }}
@endif
@stop`
Any idea how to restore my wiki?
If not: it's not a major issue. I do have a plenty of backups of the VM running the wiki.
Exact BookStack Version
25.02.5
Log Content
No helpful entries
Hosting Environment
Debian 12 (bookworm) VM served by Proxmox
apache 2.4.62
php 8.3.21
Proxy: Nginx Proxy Manager
@ssddanbrown commented on GitHub (May 27, 2025):
Hi @Jens-TGS,
This usually occurs when there's an issue with file permissions of certain files/folders.
I've advise:
.phpthat exist in thebootstrap/cachefolder relative to your BookStack install location.@Jens-TGS commented on GitHub (May 27, 2025):
Dear Dan,
thanks a lot for the quick advices. I did follow them, unfortunately they did not solve my issue.
Here is how the /var/www/bookstack folder looks like at the moment:
Any other ideas about the root cause?
BR, Jens
@ssddanbrown commented on GitHub (May 27, 2025):
Ah, okay.
git statusfrom your BookStack install folder?git log -n 1from your BookStack install folder?ls -alh bootstrap/cachefrom your BookStack install folder?ls -alh storage/framework/views | headfrom your BookStack install folder?@ssddanbrown commented on GitHub (May 27, 2025):
Also, possibly related to #5433.
Worth checking your PHP packages are updated and aligned, as from that thread the finding was that differing package versions could lead to this. Could be likely in this case since it looks like you're not just using standard debian packages for PHP (I'm assuming deb sury packages?).
@Jens-TGS commented on GitHub (May 27, 2025):
Thanks a lot for your posts. I really do appreciate your support.
I did read #5433, but did not get any advice how to proceed here. Yes, my PHP packages are deb sury packages:
And everything is up to date (and was also before):
Coming to your first post from today. Here are the requested outputs:
From git status I believe all files are modified (output truncated):
But if I do have a look at the details, just the access rights are modified:
Other requested outputs:
Run again update process:
@ssddanbrown commented on GitHub (May 27, 2025):
Thanks @Jens-TGS for the detail.
That's all looking generally fine though, no surprises. Gonna have to dig into things a little more.
php -r "echo token_get_all('cat')[0][0] === T_INLINE_HTML ? 'pass' : 'fail';"?git config core.fileMode falseto ignore file permission changes then re-confirm thegit statusoutput. Should be much reduced in output lines.@Jens-TGS commented on GitHub (May 27, 2025):
Of course, here are the requested additional details:
I'm not the biggest expert in apache2 and which version it is running, but I believe, it is the reported version, since nothing else is installed:
Thanks a lot for looking into my issue!
@ssddanbrown commented on GitHub (May 28, 2025):
Thanks @Jens-TGS again for the clear responses.
All looks okay there too!
I was initially a bit suspicious of that different
php-commonpackage info, but looking at deb sury repo that looks fine.I'm at a loss, not sure what further to (reasonably) check.
At this stage, I might need to attempt replication of the same environment.
What architecture are you running here? Based upon being a proxmox based VM I'd assume standard x86_64?
Just want to check though in case I'm assuming wrong.
@Jens-TGS commented on GitHub (May 28, 2025):
Hi @ssddanbrown,
thanks again for having a look on my issue!
Yes, it is standard x86_64. What do you need?
BR Jens
@ssddanbrown commented on GitHub (May 30, 2025):
Okay, I just tried to replicate this environment.
Debian 12 LXC container on proxmox with deb sury repo using apache and mod-php, with the exact same
dpkg -l | grep phpoutput.No noticeable issues. Can't reproduce.
Makes me think it's more likely something specific to this environment and configuration.
Not sure what to check next though.
@Jens-TGS commented on GitHub (Jun 6, 2025):
Dear Dan,
thanks for replicating my environment and rolling out the tests.
In the meantime I reverted my wiki VM back to a state of an older backup and updated the bookstack app again. Now everything is working again. Data loss is small, since the wiki was not used often in the affected time slot.
If you are interested to narrow down the issue ether way, I might be able to provide you a backup of the VM including the issue.
@Jens-TGS commented on GitHub (Aug 1, 2025):
Dear Dan,
I'm still facing this issue after each update. With 25.05.2 I did a complete re-installation of BookStack and restored a backup. Everything was working find then. But after updating to 25.07 today, again the start page looks like this:
Any suggestions?
Thanks a lot!
Jens
@ssddanbrown commented on GitHub (Aug 1, 2025):
Hi @Jens-TGS,
Do you have any active customizations? Anything in the
/var/www/bookstack/themesfolder?Some of that shared code looks kind of strange, like markdown has been mixed with template code, and I'm not sure where that would have come from.
@Jens-TGS commented on GitHub (Aug 2, 2025):
Hi Dan,
thanks for your response. No, no active customizations.
/var/www/bookstack/themesis empty except the.gitignorefile. I also do have not much content in the wiki yet (mainly my IT stuff documentation).My main question is: how do I get rid of this issue, if it seems, that the problem moves also, if I do a backup and restore in a fresh installation?
Any recommendations?
BR, Jens
@ssddanbrown commented on GitHub (Aug 4, 2025):
@Jens-TGS Generally I've seen this occur when there's either file permission issues or php extension & extension lib version mismatches.
There's some really strange things though in both examples of what you have shared, which I would not expect at all.
For example, I don't know why there's the
@christopherttext, since that string does not appear in the repo, and is the username of someone who has previously contributed to the project.@Jens-TGS commented on GitHub (Aug 5, 2025):
@ssddanbrown That sounds really weired. Are you interested in narrowing down the issue or is your recommandation again a clean install and restoring a backup?
@Jens-TGS commented on GitHub (Sep 28, 2025):
@ssddanbrown Any updates on this issue in the meantime? Still not able to update to a newer version here .. :-(
@ssddanbrown commented on GitHub (Oct 5, 2025):
@Jens-TGS No, sorry.
Feel free to send a link to a VM backup file (where the issue exists) to my email (Shown when viewing my GitHub profile).
@Jens-TGS commented on GitHub (Oct 6, 2025):
@ssddanbrown Thanks a lot for providing this opportunity.
I just wanted to create the VM backup file for you. Installed bookstack version was 25.05.2.
I did take a snapshot and tried to do the latest update to 25.07.3 to see, if my update issue is still reproducible.
And: it is not.
In the meantime I also rolled back to my snapshot and gave the new update process with bookstack-system-cli a chance and also this is working.
Did you do any changes which could explain, that my issue seems to be gone in the meantime?
@ssddanbrown commented on GitHub (Oct 13, 2025):
@Jens-TGS Good to hear things are working!
No, Can't think of any changes which would affect this.
My gut instinct is that there was a bug or something odd/off in regards to a specific dependency in your environment, which has since been patched/changed/updated (or a process was using an old library in memory maybe).