As I figured it out and it was pointed out to me, the wiki uses new caches per
virtual server so I just rolled with it and created a new namespace for the
additional virtual server (I can definitely see the benefits to it working like
this) and therefore don't have to worry about what's being updated on the
virtual site. It has also given me more freedom. I think my initial idea of
sharing the content and application on two different sites probably wasn't
wise.
After I restarted IIS I got all the caches cleared and I'm satisfied with how
it's working. I don't foresee someone using the second namespace from the
default site and if they do it really isn't a problem. In the robots.txt file
I will block that directory so it doesn't get spidered by the big search
engines.
The only issue with this is the css but I read on FlexWiki that it is being
sorted out for v2.0 so that other sites that share the application can use its
own css.
Despite me trying to put a square peg into a circle hole, this is all very well
thought-out because there always seems to be another way to run FlexWiki if it
doesn't first work the way you want.
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
