I believe this is caused by a path naming issue between MacOS and Linux/Unix…
I created the “2021-07-24-Sat-Dane/Janna Wedding – event” folder on my Mac, mapped (SMB) to my unRaid NAS.
NOTE the “/” in the filename - just habit. Obviously that’s a path separator on Linux, but isn’t on a Mac (which uses “:”).
So on the unRaid box, the actual dirname was “2021-07-24-Sat-Dane:Janna Wedding – event” with the colon - that is hidden from the Mac side and displays as the “/”.
As nearly as I can tell, something in the “colon” confuses things.
I renamed the folder in question to have just a hyphen ("-") in that spot and resynced - now the directories appear properly (although I haven’t gotten them to populate fully).
Well, that’s the thing… On the NAS where PhotoStructure was running, the directory name had a “colon” - it should be legal filename character on Linux I believe.
But it seemed to confuse Photostructure.
Now my Mac interprets that colon as a “/” for display, but again, didn’t treat it as a path separator…
But things got confused.
I’m thinking that you may need to check for “:” and escape it or something, but this is a fairly edge case.
Just wanted to bring it up as it has taken me a while playing with it to figure out why I couldn’t walk down this one directory tree and it would “jump” to the bottom.
(Also, I checked and there really isn’t a way to “escape” a forward-slash in a filename on POSIX systems, so I don’t think that’s what we’re fighting here.)