[SOLVED] overlapping thumbnails in nested albums

cyann

Joined: 2013-10-24
Posts: 3
Posted: Thu, 2013-10-24 15:19

Hi! I am having some issues with the way thumbnails are displayed in nested albums. Please have a look at the following if you will:

*This is the main gallery index:
http://costumenetwork.com/gallery3/
* This is a 'nested' album:
http://costumenetwork.com/gallery3/61
* This is one of the albums in the 'nested' album above (I will call this the 'leaf' album below):
http://costumenetwork.com/gallery3/61/album173

As you can see, both the main gallery index and the 'leaf' album display thumbnails correctly. They also both have the same number of thumbnail columns.

However, the 'nested' album has a higher number of thumbnail columns, and as a result thumbnails are overlapping both in horizontal and vertical directions. I would like to get this album (and others like it) to display the same way that the main gallery index and 'leaf' albums are being displayed, but I haven't been able to find where to configure this behaviour as of yet?

Any help greatly appreciated!
Isabeau

 
floridave
floridave's picture

Joined: 2003-12-22
Posts: 27300
Posted: Thu, 2013-10-24 15:37

I don't see any isse with the * This is a 'nested' album:
http://costumenetwork.com/gallery3/61

I notice that some thumbs are of different sizes. Some are 100 and some are 160. Perhaps that is your issue?
Screenshot with your issue might help.

Dave

____________________________________________
Blog & G2 || floridave - Gallery Team

 
cyann

Joined: 2013-10-24
Posts: 3
Posted: Thu, 2013-10-24 17:25

Mmm. It seems that the issue resolved itself after I upgraded to the latest release. My bad for not trying that earlier...

I still have a screenshot of the 'old' behaviour though (see first attachment). That was on gallery 3.0.5. The other screenshot (and current behaviour) is on gallery 3.0.9

 
cyann

Joined: 2013-10-24
Posts: 3
Posted: Thu, 2013-10-24 17:27

And... of course the screenshots are in reverse order ;-)

Anyways, thanks for your reply. Problem resolved for now!