Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: [Solved, sort of]: 1.3.1 after upgrading from 1.2.1 some images are broken  (Read 3611 times)

0 Members and 1 Guest are viewing this topic.

Galapagos

  • Coppermine newbie
  • Offline Offline
  • Posts: 13
    • http://www.tomdegoeij.com

Last week I updated my version of CPG from version 1.2.1 to version 1.31. At the beginning everyhing looked just fine, but tonight I noticed something strange. Some pictures are not viewable anymore. When viewing the album list the pictures are displayed as a 'dot' (just a couple of pixels). When clicked upon you won't see the picture either. Again just a couple of dots.

I figured out it probably has something to do with illegal characters in the filenames... The files I'm talking about have filenames like:
!cid_image008.jpg@01C42579[1].JPG@01C42579[1]
I know that's a really weird filename, since it doesn't even have an extension like .jpg or something. I don't know how it was possible addings these files to the album in the first place, but it surely was possible using CPG 1.2.1. There were no problems at all adding the pictures and also no problems at all viewing them. But after upgrading to version 1.3.1 I have the problems mentioned above.

For an example please go to this album on my CPG-site: http://tomdegoeij.xs4all.nl/coppermine/thumbnails.php?album=143
Username: testaccount
Password: password

The first picture shown on the first page on the album is named on the server like this:
/coppermine/albums/feestjemarieke2004/thumb_!cid_image001.jpg@01C42579[1].JPG@01C42579[1]
When using 1.2.1 it appeared on the page like this:
http://tomdegoeij.xs4all.nl/coppermine/albums/feestjemarieke2004/thumb_%21cid_image001.jpg%4001C42579%5B1%5D
After upgrading to 1.3.1 it appears like this:
http://tomdegoeij.xs4all.nl/coppermine/

So it looks like a 1.3.1 can't deal with strange filenames and 1.2.1. Since my site contains over 20,000 pictures it would be a hell of a job just to find out what pictures are faulty. Perhaps someone from this forum can hell me out on this. If the pictures worked on 1.2.1, they should be able to work on 1.3.1 I'd say.

Thanks a lot in advance!

update: using PHPMyAdmin I found out that the 22 pictures in the album mentioned above are probably the only pictures affected. So I can 'solve' the problem quite easily by changing the filenames manually. Still i think this thread is useful since other people might be dealing with the same problem. And I haven't figured out yet what causes the problem... It might be the pictures not ending on .jpg or maybe even the @, [ or ] in the filenames.
« Last Edit: July 30, 2004, 04:27:14 pm by GauGau »
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: 1.3.1 after upgrading from 1.2.1 some images are broken
« Reply #1 on: July 30, 2004, 08:14:57 am »

I can't understand how you could have been able to upload files without extension in the first place, using cpg1.2.1
Now that the situaton is as it is, I can't think of another solution than the one you already outlined: renaming the files both on your server and in the coppermine database. Sorry.

GauGau
« Last Edit: July 30, 2004, 04:30:59 pm by GauGau »
Logged

Galapagos

  • Coppermine newbie
  • Offline Offline
  • Posts: 13
    • http://www.tomdegoeij.com
Re: 1.3.1 after upgrading from 1.2.1 some images are broken
« Reply #2 on: July 30, 2004, 01:15:05 pm »

Hi GauGau,

Thanks for looking at the problem. For me it's okay, since I can fix it quite easily. It's indeed really weird that I was able to upload those pictures in the first place. I didn't use any mods or something like that, and as far as I know I didn't mess with the config options too much.

Nevertheless, since I'm probably the only one with this problem this thread can be closed :-)

Cheers!
Logged
Pages: [1]   Go Up
 

Page created in 0.021 seconds with 21 queries.