I did a quick check with a folder the same name as the siteaccess and had no problem. I'm going to guess that it's your rewrite rules. Do they look something like this (all the "static" directories would have to be whatever you configured and the root path would have to be correct):
I found another post that mentioned the CachedSiteAccesses config param and that worked for the building of the cache files. Here is my setting.
[CacheSettings] CachedSiteAccesses[]=reviews
I do have another problem though. Cache files are being generated for folders that I do not want to be cached. for example, I haven't configured the /test folder to be cached, but cache is being built. Also, The cache doesn't seem to be rendering properly. If I create a sub item in the folder test and view the cache, then the links for the sub items are not displayed, but if I delete the cache and then view it without the cache then the subitem links show up.
It looks like some of the cache is not being updated. in the static/review/test folder there is an index file. I have monitored it and it seems to be updating.
There are some files in the static/reviews/content/full/view/... whick I believe are internal parts of the page that are not being updated. Can anyone help me figure out how to get everything to update properly?
I'm having a similar problem to one that Stephen mentions, namely,
cache is being generated for content that should not be cached.
Even if I only designate a single node for StaticCache'ing, after a bit
my cache directory fills up with a ton of other rubbish. Cache is even being created for registering users, and this just can't be right.
Anybody else seeing this, or know what's going on? Or, more importantly, know how to fix it?
There are several bugs in the static caching mechanismn, see my bug report: http://ez.no/community/bugs/static_cache_uses_old_cache_to_create_new_cache_on_publishing