update to 22.11: dark mode toggle, shortcuts, search not working #3377

Closed
opened 2026-02-05 06:32:35 +03:00 by OVERLORD · 8 comments
Owner

Originally created by @mb1811 on GitHub (Dec 1, 2022).

Attempted Debugging

  • I have read the debugging page

Searched GitHub Issues

  • I have searched GitHub for the issue.

Describe the Scenario

updating from 22.10 to 22.11 - following your instructions - ran fine. No errors.
Settings menu shows v22.11.

After logging in I get a 405 page when choosing from the menu.

Clicking the shortcut item from menu, I get a bookstack message: Page not found.

The central search works the same as in v22.10. New search is not available

Exact BookStack Version

22.11

Log Content

nothing found.

PHP Version

7.4.33

Hosting Environment

Debian 11

Originally created by @mb1811 on GitHub (Dec 1, 2022). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario updating from 22.10 to 22.11 - following your instructions - ran fine. No errors. Settings menu shows v22.11. After logging in I get a 405 page when choosing from the menu. Clicking the shortcut item from menu, I get a bookstack message: Page not found. The central search works the same as in v22.10. New search is not available ### Exact BookStack Version 22.11 ### Log Content nothing found. ### PHP Version 7.4.33 ### Hosting Environment Debian 11
OVERLORD added the 🐕 Support label 2026-02-05 06:32:35 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Dec 1, 2022):

Hi @mb1811,

Please can you provide the output of running git status within the top folder of your bookstack install?

@ssddanbrown commented on GitHub (Dec 1, 2022): Hi @mb1811, Please can you provide the output of running `git status` within the top folder of your bookstack install?
Author
Owner

@mb1811 commented on GitHub (Dec 1, 2022):

git status
Aktualisiere Index: 100% (1582/1582), fertig.
Auf Branch release
Ihr Branch ist auf demselben Stand wie 'origin/release'.

Änderungen, die nicht zum Commit vorgemerkt sind:
  (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)
  (benutzen Sie "git restore <Datei>...", um die Änderungen im Arbeitsverzeichnis zu verwerfen)
	geändert:       app/Config/snappy.php
	geändert:       public/dist/export-styles.css
	geändert:       resources/views/exports/book.blade.php
	geändert:       resources/views/exports/chapter.blade.php
	geändert:       resources/views/exports/parts/chapter-item.blade.php
	geändert:       resources/views/exports/parts/custom-head.blade.php
	geändert:       resources/views/exports/parts/meta.blade.php
	geändert:       resources/views/exports/parts/page-item.blade.php
	geändert:       resources/views/layouts/parts/export-body-end.blade.php
	geändert:       storage/clockwork/.gitignore

Unversionierte Dateien:
  (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken)
	.env.bak
	.env~
	DEADJOE
	app/Config/snappy.php~
	public/dist/export-styles.css.backup
	public/dist/export-styles.css~
	resources/views/exports/book.blade.php~
	resources/views/exports/chapter.blade.php.backup
	resources/views/exports/chapter.blade.php~
	resources/views/exports/page.blade.php~
	resources/views/exports/parts/chapter-contents-menu.blade.php~
	resources/views/exports/parts/chapter-item.blade.php.backup
	resources/views/exports/parts/chapter-item.blade.php~
	resources/views/exports/parts/custom-head.blade.php~
	resources/views/exports/parts/meta.blade.php_backup
	resources/views/exports/parts/meta.blade.php~
	resources/views/exports/parts/page-item.blade.php#
	resources/views/exports/parts/page-item.blade.php.backup
	resources/views/exports/parts/page-item.blade.php~
	resources/views/layouts/export.blade.php~
	resources/views/layouts/parts/export-body-end.blade.php~

keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder "git commit -a")
@mb1811 commented on GitHub (Dec 1, 2022): ``` git status Aktualisiere Index: 100% (1582/1582), fertig. Auf Branch release Ihr Branch ist auf demselben Stand wie 'origin/release'. Änderungen, die nicht zum Commit vorgemerkt sind: (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken) (benutzen Sie "git restore <Datei>...", um die Änderungen im Arbeitsverzeichnis zu verwerfen) geändert: app/Config/snappy.php geändert: public/dist/export-styles.css geändert: resources/views/exports/book.blade.php geändert: resources/views/exports/chapter.blade.php geändert: resources/views/exports/parts/chapter-item.blade.php geändert: resources/views/exports/parts/custom-head.blade.php geändert: resources/views/exports/parts/meta.blade.php geändert: resources/views/exports/parts/page-item.blade.php geändert: resources/views/layouts/parts/export-body-end.blade.php geändert: storage/clockwork/.gitignore Unversionierte Dateien: (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken) .env.bak .env~ DEADJOE app/Config/snappy.php~ public/dist/export-styles.css.backup public/dist/export-styles.css~ resources/views/exports/book.blade.php~ resources/views/exports/chapter.blade.php.backup resources/views/exports/chapter.blade.php~ resources/views/exports/page.blade.php~ resources/views/exports/parts/chapter-contents-menu.blade.php~ resources/views/exports/parts/chapter-item.blade.php.backup resources/views/exports/parts/chapter-item.blade.php~ resources/views/exports/parts/custom-head.blade.php~ resources/views/exports/parts/meta.blade.php_backup resources/views/exports/parts/meta.blade.php~ resources/views/exports/parts/page-item.blade.php# resources/views/exports/parts/page-item.blade.php.backup resources/views/exports/parts/page-item.blade.php~ resources/views/layouts/export.blade.php~ resources/views/layouts/parts/export-body-end.blade.php~ keine Änderungen zum Commit vorgemerkt (benutzen Sie "git add" und/oder "git commit -a") ```
Author
Owner

@ssddanbrown commented on GitHub (Dec 1, 2022):

@mb1811 I don't think you're getting the latest files downloaded, since the first update command to pull the latest changes would probably conflict with your local environment, since there are a bunch of files with detected changes.

Have you made changes to the listed (At the top) files? and if so do you need to retain those?

@ssddanbrown commented on GitHub (Dec 1, 2022): @mb1811 I don't think you're getting the latest files downloaded, since the first update command to pull the latest changes would probably conflict with your local environment, since there are a bunch of files with detected changes. Have you made changes to the listed (At the top) files? and if so do you need to retain those?
Author
Owner

@mb1811 commented on GitHub (Dec 12, 2022):

Thanks for that hint. I'll check those files later - for now we need a running system to do our documentation.

@mb1811 commented on GitHub (Dec 12, 2022): Thanks for that hint. I'll check those files later - for now we need a running system to do our documentation.
Author
Owner

@mb1811 commented on GitHub (Dec 13, 2022):

I tried to backup all those files I did minor changes on (mostly the export files), then deleted them.
I did the update again - same errors-.

I then backed up the database and moved the install folder to a backup-location.
Finally I did a reinstall with the old database - that worked.

As we need some changes especially in the export (left margin on an printed file, some css changes like fontsize, etc..) - is there a way to avoid those errors and to keep our files?

@mb1811 commented on GitHub (Dec 13, 2022): I tried to backup all those files I did minor changes on (mostly the export files), then deleted them. I did the update again - same errors-. I then backed up the database and moved the install folder to a backup-location. Finally I did a reinstall with the old database - that worked. As we need some changes especially in the export (left margin on an printed file, some css changes like fontsize, etc..) - is there a way to avoid those errors and to keep our files?
Author
Owner

@rokkondic commented on GitHub (Dec 19, 2022):

Hello,
I seem to be having the same issue. I updated version 22.10 to version 22.11.1. The update went fine, except for these issues:

  • The search preview is not working
  • When I try an toggle to light/dark mode I get this error:

MicrosoftTeams-image (1)

Some additional information:

  • PHP version: 7.4.32
  • Server: Ubuntu 18.04.6 LTS
  • Git status:
    MicrosoftTeams-image (2)
@rokkondic commented on GitHub (Dec 19, 2022): Hello, I seem to be having the same issue. I updated version 22.10 to version 22.11.1. The update went fine, except for these issues: - The search preview is not working - When I try an toggle to light/dark mode I get this error: ![MicrosoftTeams-image (1)](https://user-images.githubusercontent.com/43110771/208425844-0a2011f7-6e84-4c30-a2dd-937aa7be8b7a.png) Some additional information: - PHP version: 7.4.32 - Server: Ubuntu 18.04.6 LTS - Git status: ![MicrosoftTeams-image (2)](https://user-images.githubusercontent.com/43110771/208426076-cf80e60d-453f-48af-8de6-27319b0d8717.png)
Author
Owner

@rokkondic commented on GitHub (Dec 28, 2022):

After a clean reinstall all the mentioned problems are gone.

@rokkondic commented on GitHub (Dec 28, 2022): After a clean reinstall all the mentioned problems are gone.
Author
Owner

@ssddanbrown commented on GitHub (Dec 28, 2022):

I will therefore close this off.

In regards to keeping customizations, please see our visual theme system which allows custom overriding/customization of application views without editing core app files.
For simpler tweaks, you can target exports via certain classes for CSS via the "Custom HTML Head Content" customizations setting. For example, a css rule of .export-format-pdf p { color: red;} would cause red paragraph text just within pdf exports.

@ssddanbrown commented on GitHub (Dec 28, 2022): I will therefore close this off. In regards to keeping customizations, please see our [visual theme system](https://github.com/BookStackApp/BookStack/blob/development/dev/docs/visual-theme-system.md) which allows custom overriding/customization of application views without editing core app files. For simpler tweaks, you can target exports via certain classes for CSS via the "Custom HTML Head Content" customizations setting. For example, a css rule of `.export-format-pdf p { color: red;}` would cause red paragraph text just within pdf exports.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#3377