mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-12 19:06:27 +03:00
Image missing error #1215
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 @madsmka on GitHub (Jun 3, 2019).
After creating a new server with bookstack version v0.26.2 and moving our database and pictures, if I were to use the picture we already have it doenst show up in the book, but if i upload a new picture the new picture works fine.
The pictures works fine in the "old books" where they already where added, but again if i try to add the picture again it doenst work.
If I look at the picture in the image selector, the picture is missing aswell. If I click on the error picture it opens the picture in a new tab fine. (It also shows the picture in the image selector list)
Steps to reproduce the behavior:
Config:
@ssddanbrown commented on GitHub (Jun 4, 2019):
Hello @madsmka,
With the server move, have you also changed domains or does the domain stay the same? Have to changed from http to https as part of this move?
Could you confirm where you uploaded your previous images to and what your current
STORAGE_TYPEvalue is in your.env?@madsmka commented on GitHub (Jun 4, 2019):
Hello
No I have not changed domain it's the same as before and no we used HTTPS before aswell.
New Server STORAGE Type: local_secure
Old server STORAGE Type: local_secure
New Server image location: /var/www/bookstack/storage/uploads/images/gallery/*
Old Server image location: /var/www/bookstack/storage/uploads/images/gallery/*
Whats weird is that the image works fine in the list, as you can see here it's just the preview thats not showing (It's also not showing if we add it to a page):
And if i click on the missing image, it opens the URL fine and shows the image:
@ssddanbrown commented on GitHub (Jun 4, 2019):
@madsmka Hmm, That's odd. It's like all the generated thumbnail sizes are not on the new server.
Within your images folders that would have been a bunch of folders like
thumbs-800or something like that with resized copies of images, were these also copied over?@madsmka commented on GitHub (Jun 4, 2019):
Yes I also copied all the thumbs, and if I click on the error preview picture it browses to the picture fine:
If I add the picture to the page, and click on the image it also browses to the image fine:
This is the things that I copied over, and there is no folder like thumbs-800 but we got scaled-840-0 and thumbs-150-150:
If I look at the new image I added that works fine, in the scaled directory is named scaled-1680- instead of the scaled-840-0 that all our old picture have but I dont know if this matters:
@ssddanbrown commented on GitHub (Jun 4, 2019):
No, That's fine, just a image size change I made in the latest release.
Could you open the browser development tools (Usually
Ctrl + Shift + I), Then view theconsoletab and then refresh a page which contains non-loading images? Should see a bunch of red messages appear in the console, If you could post those red messages that would be great.@madsmka commented on GitHub (Jun 4, 2019):
It just shows this message:
@ssddanbrown commented on GitHub (Jun 4, 2019):
@madsmka Thanks, Unfortunately that does not tell us too much, but I think I know what this may be. I've done some testing on my side and could reproduce something similar when the web server did not have execute permissions on the sub-folders (
scaled-840-0etc...). Does apache have write & execute on all image directories?@madsmka commented on GitHub (Jun 4, 2019):
I went through the subfolders and some of them was indeed missing Write&Execute. I found some where the permissions was correct, I tried testing the pictures in that folder and they worked like they should. So I chmod -R on the gallery folder to fix the permissions on the subfolders which solved the problem!
I don't know how this happend, maybe I forgot an argument while copying some of the folders.
Thank you so much for the fast help, and good job on version 0.26 it looks great! :)
@ssddanbrown commented on GitHub (Jun 4, 2019):
@madsmka Awesome, Happy to hear that done the job. Thanks for the kind feedback.