It's actually a combination of two small errors, caused by the switch from BeanShell to Groovy scripting. Replace the skin's common.css and cssinit.groovy files with the attached versions, and see how that works for you.
Jeff, something else. Is there a reason why the fix mentionned in the thread "ZigZag Doing weird stuff. Posted: 9 Jan 19" is not implemented in the latests versions of the ZigZag skin ?
I re-generated one of my projects with version 2.2.0 on jAlbum 29.1.10 and had to manually add the "start = 0" fix in "common-header.inc" to solve my problem... after it took me a few hours before remembering what the problem was.
I'll be out for the week-end, but you can have a look at the related project at www.francoiseseffer.com.
This is a site I created for my wife to share her artistic projects. As you will see, there is a main folder containing only second level folders which in turn contain the images and text.
In each subfolder there is a menu, similar to the one in the main folder, leading directly to other subfolders or back to the main one. This is done via webpages containing redirection commands in each subfolder.
The problem was that when generating the subfolders "index.html" files (from "index.htt") the </ja:iterator category= "webPage, folder"> command in the "menu" div didn't take all the redirection webpages that were present, but only part of them... unless I added the "start=0" parameter within the iteration (in "common-header.inc").
First things first.... David has introduced a new bug into ZigZag v.2.2.1. I've emailed him about it. The common-header.inc file contains a line of debugging code that should have been removed. Edit that file and delete line 37:
I've built a little test project using your "redirection" approach to planting an album-wide menu on each page, and it appears to do what you want. Each folder, when viewed, shows a menu with links to each of the other folders, and to the album home. I didn't have to modify the skin files at all, and the album builds without any errors.
Jeff, I extended your test program to 8 subfolders, and... bingo, when all 8 appeared on the main folder, only 5 of them showed up in each subfolder, unless I added the start=0 command in the common-header file.
By the way, I only found the debugging line when I uploaded version 2.2.1, so I didn't notice it in 2.2. Deleted now.
You're right, and this is fascinating. My challenge will be to explain this to David in a way that doesn't make his head explode.
That number, 5, was suspicious, so I played a hunch. And I was right. For reasons unknown, the jAlbum core is using the setting for the number of thumbnail columns to control that automatic file iteration. It shouldn't be - these are totally unrelated things.
That setting is grayed out, so you can't change it. Edit the skin's skin.properties file, and change enableThumbnailLayout to true. Close the project, open it again, go to the Settings > Pages tab, and change the Columns setting to 99. Now make the album. I've uploaded the result in my test album, with 8 folders:
Rainy day here in Belgium ! So I went back to my computer... just to confirm you that everything works fine in my project with your recommandations. So, no need for start="0" anymore. Will the change be implemented in skin.properties ?
Will the change be implemented in skin.properties ?
No, because this is really a jAlbum core bug that David will need to address. The skin, and your project, should work just fine without having to "tinker" with the skin coding. Changing skin.properties is just an easy, temporary work-around.