- Issue created by @kopeboy
- 🇮🇹Italy kopeboy Milan
No error in the logs nor in the browser console whatsoever, using Chrome on macOS.
- 🇷🇺Russia i-grou
Have the same issue on my site. Any suggestions how to fix it?
- 🇧🇪Belgium ScriptCircle
Hi, thanks for repoting the bug. I'm working on fixing that to be delivered. next week.
- Status changed to Fixed
23 days ago 11:55am 3 January 2025 - 🇷🇺Russia i-grou
Thanks for that fix @g.mustapha, now there is no anything pointing to the real image in the Page Inspector tool:
At the same time I can still see the direct image url in the page source:
Basically it means that there is no protection for the image, as it's possible to get to the page source and get any image from there (it's also easy to write a script for that). Are there any other ideas to implement in the nearest future to achieve real protection?
- 🇧🇪Belgium ScriptCircle
There is a problem with the image you attached. It doesn't make sense if your field HTML has a Canva tag that means you can't see what's inside. The bout images are from different files. The first one is from a fuels where protect_photo is active, and the second one is from olde field. Try to reactivate the image view config on the corrupted file.
- 🇷🇺Russia i-grou
Well, I've tried to uninstall a module and install it again - results are the same. When I use Inspector/Console (Ctrl+Shift+I) I can see a canvas instead of image. But when I look at the page source (Ctrl+U) I can see normal img tag with direct url in it.
And it's not surprising actually. As I've checked the source code of your module and can clearly see that it relies on js library. So the source html was never meant to be protected.
As a conclusion I can say that this module offers good protection for images from average users. At the same time it provides zero protection from tech-savvy guys. Maybe you should note it somewhere in the module description.