I've noticed in the past that when I've occasionally downloaded my uploads from Caedes they wont open in some photo editing software until the files are renamed from JPG to PNG.

Naturally not all artists here upload in PNG format like me so I don't always have this problem when editing them for personal use.

Here's a few examples for interested people to try it out for themselves Winter by picardroe marked as JPG and is genuine, however Salty Spray by corngrowth is marked JPG but has to be renamed PNG so PhotoFiltre, InfanView etc can open them. For final confirmation try one of my mine [promotion unintended] The lady poses #2 marked as JPG but needs to be renamed PNG. When the irregular images mentioned are downloaded the file properties read JPG but this is contradictory as the "online image info type" reads PNG, btw I've not had any problems with thumbnail images.

I've noticed this minor defect for some time now and am interested to know what other people think and would appreciate a response from the Caedes team when available please.

Ditto. I've noticed the same thing...I have to rename them, as well.

Same here for some time now. If I try to open them with photoshop elements I get the message: Could not complete your request because of an unknown or invalid JPEG marker type is found. My workaround is to open them in MS Paint and use the save as command as a jpg with a different name before I can open them with other programs.

It's equally simple just to retype the file manually Wendell and it's always a good idea to confirm type what it is.
Simply left click on blown up thumbnail and right click on View Image Info before downloading if your using the Mozilla browser.

I have.. no idea, unfortunately.

As to whether or not..

A change in site image software is the culprit.. is this a recent occurrence?


And I've noticed similar when I've downloaded some member's images to perform some edits for commenting/feedback purposes.. and have done as Wendell; aka Eubeen has done above, didn't think to change file extensions.


However. on the time frame when this started to happen occur.. I can't recall.


Erhm.. at the risk of sounding dumb.. what is the exact nature of the 'complaint' here, for lack of a better word?

Do.. the images in question.. function differently and once again, apart from bringing them into an image editor?

For example.. muck things up on the front of the file associations with your OS, and/or relevant programs/software?

(I've not been/did not pay too much attention to this possibility, using the workaround as described and mentioned above and just carried merrily on my creative way.)

The "problem" seems to have popped up sometime back in September, 2013.

Danke, sir.

The timing might then just be related to the move to cloud storage for the site.

And in turn, perhaps.. the image display software that the site uses.


Maybe.. just speculating on the more probable reasons.


If this is an issue for some, perhaps, the topic/subject might be best served and moved to the Feature Bloat / Bug Squash section? (Sorry, I can't physically move threads/discussions.)

Or.. PM *caedes directly as an alternative.

"My workaround is to open them in MS Paint and use the save as command as a jpg with a different name before I can open them with other programs."

I ended up doing what Phil; aka gonedigital suggests.. and that is/was.. when in MS Paint, saved as PNG/png file. So.. essentially.. I ended up renaming/changing the file extension to what the original file was in the first place.

@Wendell; aka Eubeen: And more importantly.. by choosing PNG/png.. no additional image compression.

It has been a while since I programmed the code that accepts image uploads. I had thought that it was converting all images to jpg format, but that appears to not be the case. I will look into it and either have it convert the images or properly name them. Thank you for the note about this.

Thanks for your response *caedes.