One gallery won't show (zpMasonry)

joho

Using ZP 1.4.2.4 with zpMasonry 1.4.2.2 I have a weird problem. I have an album that has 108 images in it. In the album overview, ZP sees 108 images. When I go to view the images, there are zero images displayed. I get no errors in the logfiles. If I go to the public (non-admin) view, nothing seems to be displayed, but viewing the source of the generated HTML seems to indicate that there are images. I've tried refreshing meta data, purging the cache, etc.

This is the *ONLY* album where this occurs, all other albums and sub-albums are fine. And the images for the weird album are there, on the server.

If I go to the "image order" tab, I get some 30 images "displayed" as "broken images" in the browser. If I click on one of them and open it up in a new tab, I get a 404. The URL is pointing to the cache, but not to a file that exists.

If I go to the "images" tab, and choose "50 images per page", I get three pages. On page 1, there is nothing displayed. On page 2 and 3, there are images displayed. So I'm guessing this has to do with an image early on in the folder that is causing some sort of issue. If I choose to display 5 images per page, the error still only occurs on the first page. So any of the 5 first images must be broken somehow. But I cannot for the life of me figure out which one and how it can stop ZP dead in its tracks.

This is really really weird!

I've tried four different browsers.

acrylian

You mean of course an "album" (Gallery is the whole site in ZP terms). Did you try a standard theme?

I added the theme name to the topic in case it is theme specific so its authors spots it (noted on the post form btw).

joho

Thanks for responding. No, I did not try a standard theme. After a few hours of digging around, I think I've found the culprit. The album displays now. This was a case of two images having invalid filenames. On disk (server), the files had some weird encoding for an umlaut character (ö). I changed that to an 'o'. That wasn't sufficient. So I searched for it in the MySQL database and corrected the filenames there too. Then I cleared the cache and refreshed all metadata for the album, and now it displays!

acrylian

Umlauts or other special chars always tend to cause problems. Although for 1.4.3 we have tried to make that more realiable. But it is always related to encoding stuff on the server as well.

If you encounter any problems you should always try a standard theme to just make sure it is not the theme.

joho

What's weird is that it "stopped" the application dead in the water so to speak. One way would be to simply display/issue the error message and then continue. Now, I don't know how or why it stopped of course, so there may be a reason why the code has to go "tits up" and fall on its back when this occurs.

I used to battle this back in 1986 when writing FidoNet software and we were using }{| to mean the Swedish language character åäö, never would I have thought this would cause issues 2012 :-)

(I'm not blaming this issue with character encoding on you, of course)

acrylian

Yeah, I am German so I know these umlaut issues.... Since some servers (and sometimes JS interfers as well) also behave differently I still mostly recommend not to use such special chars in file/folder names, even if it acutally should work nowadays...;)