Your workaround is the correct one. Use the jAlbum uploader to handle the independent projects, like
events,
roads, and so on. For the top level, do the uploading by hand.
I have the same situation with my skin demo site, so this is familiar territory. Here's what's happening....
The
zrwon project, on its own, has no folders. It sends its output to:
/Volumes/1M2x3/WebDev/zrwon/
If you then ran the uploader, that's all it would upload. It wouldn't see
events,
roads, etc.
But now, your
events project plants its output here:
/Volumes/1M2x3/WebDev/zrwon/events/
Hey, presto, that is now part of the output directory of
zrwon. Now, the uploader says, "Oh, this
events folder is part of the output of this project, so I need to upload it."
In short, what you're doing is hanging those smaller projects like ornaments on a Xmas tree. The advantage, of course, is that you can preview the entire site locally, and it all works. But it confuses the daylights out of the uploader.
