mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-07 03:09:44 +03:00
v23.08.2 Application Homepage Setting Not Working #4207
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 @2devs1code on GitHub (Sep 13, 2023).
Describe the Bug
when I go to the base URL, I want the system to default to /books. This had worked for me prior to the upgrade to 23.08.2. Previous version is 23.06.2. Now I just get some default page showing popular pages, books, and chapters along with a very noticeable Page Not Found across the top of the page, above those other sections. There is a book that is published that allows unauthenticated users to see and read it. This does not show up.
After logging in as an admin and going to the base URL, I get the same behavior.
I have also set the default page to shelves and specific pages with no change in behavior.
Steps to Reproduce
Go to settings | customization. Set application homepage to books. Go to default url and note this is not the books you expected to see.
Expected Behaviour
I expect the base URL to display the contents of /books or anything else I choose after making the application homepage change.
Screenshots or Additional Context
Note the URLs for the base site vs /books
Browser Details
various forms of chromium and firefox
Exact BookStack Version
23.08.2
@2devs1code commented on GitHub (Sep 13, 2023):
@ssddanbrown commented on GitHub (Sep 13, 2023):
Hi @2devs1code,
This is not something I've been able to reproduce.
Can you confirm:
git status && git log -n 1from your BookStack install.ls -alh bootstrap/cachefrom your BookStack install (Assuming a linux system).@2devs1code commented on GitHub (Sep 13, 2023):
From the responsible party:
@ssddanbrown commented on GitHub (Sep 13, 2023):
@2devs1code For the update commands output, was that the output of the first run or a re-run? Also, since it's not shown, does the
composer install --no-devstep complete without error?@2devs1code commented on GitHub (Sep 13, 2023):
re-run
:~/bookstack$ composer install --no-dev
INFO Discovering packages.
barryvdh/laravel-dompdf ..................................................................................................................... DONE
barryvdh/laravel-snappy ..................................................................................................................... DONE
intervention/image .......................................................................................................................... DONE
laravel/socialite ........................................................................................................................... DONE
laravel/tinker .............................................................................................................................. DONE
nesbot/carbon ............................................................................................................................... DONE
nunomaduro/termwind ......................................................................................................................... DONE
socialiteproviders/manager .................................................................................................................. DONE
62 packages you are using are looking for funding.
Use the
composer fundcommand to find out more!INFO Application cache cleared successfully.
INFO Compiled views cleared successfully.
:~/bookstack$ php artisan migrate
Do you really wish to run this command? (yes/no) [no]
❯ yes
INFO Nothing to migrate.
:~/bookstack$ php artisan cache:clear
php artisan config:clear
php artisan view:clear
INFO Application cache cleared successfully.
INFO Configuration cache cleared successfully.
INFO Compiled views cleared successfully.
:~/bookstack$ git status && git log -n 1
On branch release
Your branch is up to date with 'origin/release'.
Untracked files:
(use "git add ..." to include in what will be committed)
.env.bak
public/apiref.html
public/sitemap.xml
nothing added to commit but untracked files present (use "git add" to track)
commit
3f473528b1(HEAD -> release, tag: v23.08.2, origin/release)Author: Dan Brown ssddanbrown@googlemail.com
Date: Mon Sep 4 12:06:50 2023 +0100
:~/bookstack$ ls -alh bootstrap/cache
total 36K
drwxrwxr-x 2 www-data www-data 4.0K Sep 13 19:53 .
drwxr-xr-x 3 www-data www-data 4.0K Sep 13 17:20 ..
-rwxrwxr-x 1 www-data www-data 14 Sep 13 17:20 .gitignore
-rwxrwxr-x 1 www-data www-data 1.6K Sep 13 19:53 packages.php
-rwxrwxr-x 1 www-data www-data 20K Sep 13 19:53 services.php
@ssddanbrown commented on GitHub (Sep 14, 2023):
Okay, and the homepage is still not working? Just asking since, if the original details were a re-run, they indicate the database migrations were not originally performed upon upgrade before.
@2devs1code commented on GitHub (Sep 14, 2023):
home page is still not working. It makes no difference if I login or not. We have the same custom headers that were present in v26. Nothing changed.
We added footer links, configured application home page and have these custom head content items:
<style> #recent-activity {display:none;} #recent-books {display:none;} #recent-pages {display:none;} #recently-updated-pages {display:none;} #recents {display:none;} #popular {display:none;} #new {display:none;} #sidebar {display:none;} #export-menu {display:none;} a[data-shortcut="revisions"] {display:none;} .tri-layout-right-contents a[href$="/delete"] + hr, .tri-layout-right-contents .actions hr + .dropdown-container {display: none;} footer a {display:block} </style>@ssddanbrown commented on GitHub (Sep 14, 2023):
Okay. When you originally mentioned:
Are you saying the other options also show the "Page not found" view? or do these work as expected?
Also:
CACHE_DRIVER=databasefix the issue?@2devs1code commented on GitHub (Sep 14, 2023):
None of the home page settings work as expected. They all go to the same bad page. No dice on the cache.
@ssddanbrown commented on GitHub (Sep 14, 2023):
Okay, really unsure what's going on here.
Let's see if we can call the homepage manually and get more detail on the issue.
Can you run the below from your BookStack install directory then share the output?:
@robertjustjones commented on GitHub (Sep 14, 2023):
@ssddanbrown thanks for your help. I'm working here with @2devs1code on this issue.
I tried your first two suggestions. Setting the homepage to Default or any of the other settings had no effect. I also tried adding
CACHE_DRIVER=databaseand separately withSESSION_DRIVER=database, with restarts after each change, also with no effect.I tried the tinker line after each of the above .env changes. In all cases, I got the following error.
Having search for any issues related to that message, I created the .config directory and the tinker line now yields
Even so, no change to the homepage error. Does "code:4" or anything else tell you something.
@ssddanbrown commented on GitHub (Sep 14, 2023):
Not really to be honest. The test indicates that most of the controller logic is working.
I'm starting to wonder if this is a routing issue.
Can you temporarily edit the
app/App/HomeController.phpfile, within your BookStack install, adding:Above this line:
dfaf6f7c13/app/App/HomeController.php (L25)Then load the homepage again. It should now just show "hello" on the homepage. If this is not the case, please could you share your apache config?
@robertjustjones commented on GitHub (Sep 14, 2023):
Having done that, I get "hello" if I go to
/index.phpbut not for/. That's still the not found page.I had a Cloudfront config that was sending errors to
index.html, which I changed toindex.php. FWIW, I've got caching disabled on everything but/uploads/which is redirecting from s3.Here's the conf, I think unedited from installation.
In the access.log, I'm still seeing some requests for
/get issued as/index.html(404) thus the error page. Since you mentioned it, I've done 2 things to try to correct that. First was adding this line to the above:And the second was to do effectively the same thing w a cloudfront function.
Still the error page.
@robertjustjones commented on GitHub (Sep 14, 2023):
Doh, I found it. More in a moment.
@robertjustjones commented on GitHub (Sep 14, 2023):
The cloudfront top-level distribution config was defaulted to index.html. Just changed it to index.php and reset all the tweaks from above. Works great... thank you so much!
@robertjustjones commented on GitHub (Sep 14, 2023):
@2devs1code go ahead and close this one. Thanks!
@2devs1code commented on GitHub (Sep 14, 2023):
thank you @ssddanbrown
@ssddanbrown commented on GitHub (Sep 14, 2023):
Thanks for confirming back the cause, and glad to hear that you found the source of the issue!