mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Wierd issue displaying book description #656
Closed
opened 2026-02-04 21:37:16 +03:00 by OVERLORD
·
11 comments
No Branch/Tag Specified
development
l10n_development
further_theme_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#656
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @sprnza on GitHub (Apr 27, 2018).
If I add this book description it doesn't show up on a book overview page (
tag is just empty), but I do see it when open up the book.
If I add some text in front of the text the issue disappears:
UPD: if a cut the added text down to
Lorem Ipsum is simply dummy text.so the description appears like this:The issue is back.
@ezzra commented on GitHub (Dec 10, 2018):
works for me, perhaps the issue is just gone in the current release?
@sprnza commented on GitHub (Dec 10, 2018):
Nope, the issue is still there.
BookStack v0.24.2 from docker image
solidnerd/bookstack:0.24.2with mariadb@ezzra commented on GitHub (Dec 10, 2018):
did you look up the database table? what does it look like there? Thats the problem with utf8, it can be scrambled anywhere from input to output, but strange that it just does not show up...
I guess, you have the same problem with all russian textes in description?
@sprnza commented on GitHub (Dec 10, 2018):
In the database it looks like this:
But I think it's because container doesn't support UTF8 in its console. test-edd is another book I added to check that cyrrillic symbols are being displayed correctly. No, the exact this string from the first post doesn't show up. If I enter another text in Russian it works like it's intended to. Moreover the string that doesn't show up on books overview page does show up when I open up the book.
@ezzra commented on GitHub (Dec 10, 2018):
ah ok, I didn't understand this because you wrote " it doesn't show up on a book overview page", I thought you are talking about the book page, not the books list. True, I can reproduce the problem on the list, mh
@sprnza commented on GitHub (Dec 10, 2018):
Yep, sorry for my English :)
@ezzra commented on GitHub (Dec 10, 2018):
workaround: just add a space to the beginning of the description field in databse, this will be cut out and it works like a charme :) But
@ezzra commented on GitHub (Dec 10, 2018):
Ok got it, the problem is in line 98 in
Entities/Book.php, I already had a feeling that it has something to do with not-multibyte-safe functions, and there it is. Just replacewith
@sprnza commented on GitHub (Dec 10, 2018):
Yay! Works!
@ezzra commented on GitHub (Dec 10, 2018):
unfortunately, thats not the only position where not mb safe functions are used, I could go on and replace them everywhere. But there is actually a performance issue using them (though to be honest, this is kind of microperformance optimizing).
So the question is, should they be replaced everywhere or should the simple functions be kept where the mb_function is not needed currently? The danger, however, is that something will change and then problems will arise again. I would vote to replace them all, what does @ssddanbrown think?
@ssddanbrown commented on GitHub (May 25, 2019):
Fixed in the next release. Thank for helping and providing info @ezzra.
I've just replaced many where user-provided input might be handled, Will just try to keep in mind to use
mb_functions where needed and handle cases as they arise.