Previous working images are now resulting to alternative text, because of gitbook image handling.
Bug description
So all my old photos and screenshots not results to alternative text. Not sure exactly when this started to happen, but my enitre gitbook is effected.
As you can see in the following image:
The image is resulting to alternative text instead of presenting the image. When we view the direct link of the image, we can see the following url:
https://www.gitbook.com/cdn-cgi/image/dpr=2,width=760,onerror=redirect,format=auto/https%3A%2F%2Facademy.hackthebox.com%2Fstorage%2Fmodules%2F171%2Fmangomail%2F1.png
if we url decode the image url the image still exsist, however somehow the url encoding and the handling of the cloud hosted image is resulting in alt text being presented.
How to reproduce
Not sure, this has happened to all my images in the entire gitbook suddenly. Either i have to replace everything or create this bug report and hopefully someone can help.
Additional context
A working image, newly inserted has a completely different link. Not sure if there is an easy way to fix this problem.
Hi @p0in7s - how are you uploading your images? Are you able to share the link to your published site?
I am uploading by directly coping it from my source. Usually by simply just using CTRL + C and vice versa with pasting the image. These images are hosted on a different cloud container. However what i noticed was that if i redid the copy and paste functionality the new image are now hosted on a different url that the ones in my blog from before. Might be the problem...
When you copy and paste the image, it should upload that image to GitBook’s file serving system, unless you’re pasting it as a URL (“/“ -> Image -> paste URL)
Can you try to download the image, and upload it from your computer and let me know if that works?
Yes, but the issue seems to stem from problems using old images and them not being properly served. Yes i can replace all the images and that works fine, however none of the old images uses the new and updated fileserver.
Can i get an update on this?
Can you share a link to your gitbook site this is happening to?
The gitbook that i have cant be published due to a lot of subscription content being hosted there, and if i publish the content its against their regulations. Maybe i can privatly invite you privately to view the page? If i can get your email?
There is currently too much sensitive information on there, which directly crosses their copyright rules
also, i tried synching the site to my github and now the images are working again, this way it uses a different image source which is why its working again.
What i can do is set up a "showcase" website that i can publish online, so you can view the image issues directly in a "simulated" website.
This was the best i could do:
This happens to everything btw, gif,png,jpg,jpeg ect ect..
Its weird. The images work fine when viewing them in raw md format, however the gitbook page returns the ALT text. I've even tried creating a new site, and importing via zip, but that returns an error. I also tried importing the site directly via github sync, but that causes issue once again on the gitbook website. Everything works fine when viewing the repo directly inside github.
Can we get some more people on this? I am not getting any response from you other than "give me link"
Github presents the images working 100%, all markdown files are presenting. I also just noticed that the published websites resolves the images working. However inside the developer spaces they do not reflect the images. So if i publish my website it works, but while editing the space where i keep my content they do not resolve the image. Im guessing this is because the preview submits a header or token of sorts to bypass the 403 error that i see when i go to the image directly inside the developer mode.
So if i inspect source and view the image it returns a 403 status code
If i publish my website and look at the page again it now returns a 200 status code (most likely) and now the image is presented. I am guessing this is because of said "token verification" that authenticates as the gitbook to view those files and now its possible to view the images.
My main issue here is that i use the gitbook privatly for my own research and other stuff. So when this is so heavily restricted in "developer mode" i can not view the images in my notes. Is there a bypass for this?
Bumping this, its quite annoying
Sorry for the slow reply—we’ve flagged the issue internally and are on it.
Quick heads-up: This repo is about published sites only. If the problem is with the editor itself, hitting up support in the app is the fastest way to get help.
I’ll update you here as soon as we have news!