jAlbum looks for skins in more than one location.
Rename the "ExhibitPlus" folder to "ExhibitPlus1", then open your project, select the ExhibitPlus1 skin and make the album.
Depending on whether the album is good, we will then decide on the next step.
totalIndexes doesn't work because all the folders are shown on the first index page and then (cols*rows) images are shown underneath it. jAlbum's calculation of the number of index pages is not always correct (e.g. cols = 2, rows = 4, 5 folders, 23 images: jAlbum thinks there are 4 index pages but there are only 3).
If you try E+ 1.5, an index that contains sub-folders and multiple index pages sometimes produces a weird navigation bar.
I did some work on this yesterday evening. I think this works. This also fixes the exception if rows or cols is 0.
In index.bsh, replace
The behavior of the built-in file iterator is perverse enough that I've pretty much abandoned it, choosing to do "my own thing," with something like getChildren(). With that, I don't have to keep referring to a cheat sheet to figure out what it's going to do.
A quick test indicates that it's behaving much better. Only one oddity - screenshot 1739 shows what you get if there are only folders at the top, and 1742 shows what you get if there are folders plus one image at the top. If there are more images than folders, you get a count of only the images.
I never used E+ even back in its heyday, so I'm not sure how it's supposed to behave. I guess what I'd expect would be a count of objects - images plus folders. But I could argue that either way....