Hi guys,
I remember posting about this issue years ago, I can't remember if it was solved or I gave up but after upgrading to the latest version of zenphoto today I noticed it's back or still there.
In Firefox if I save an image, the browser wants to name it i.php.jpg.
It only does it if I use the right-click menu; if I use ctrl+s it uses the right image name. Very weird.
It also uses the right image name in Chrome and IE, but a lot of my website's users use Firefox.
For example: http://www.dualmonitorbackgrounds.com/albums/celebrities/jenniferlawrence-9.jpg
Sorry, I cannot reproduce this in any browser. Downloading a php file would only occur if you set the full image to be protect so it would be served via a php script instead of linked directly.
Of course if you try to download the image from the thumb view that of course would download a php file…
Thanks for the replies. I couldn't reproduce it from the link I gave either, so it appears the referrer might affect it.
I was able to reproduce it by going to an album page (http://www.dualmonitorbackgrounds.com/5_minutes_away/) and clicking on a thumbnail, then clicking on the image on the image page, then right-clicking to "Save Image As...", via Firefox. The image was added months ago.
Are you able to reproduce it with those steps?
Indeed I can using FireFox but Chrome works correctly. I looked at the HTML of the page. The image link is:
[img]/zp-core/i.php?a=5_minutes_away&i=toscana-casa.jpg&cw=0&ch=0&q=100&wmk=!&check=ebe531e718459462323097d4db96cf3da5ab05c5[/img]
Which is an image processor link. Not sure why that is still there. Zenphoto redirects the link to the cache to load the picture if the cache is not protected. That apparently is what is happening here. Chrome pays attention to the changed "link" and shows you the image name. Apparently FireFox is not so astute.
Actually, in this case it is not changing even though the image is cached. So one of two things are going on:
You have set the protected image cache option so that these URLs always go through the image processor
There is something caching the page somewhere along the path from Zenphoto to the browser. It would not be the Zenphoto cache since that is invalidated if there is an image processor URI on the page. It would have to be a server cache or proxy cache.