Thanks for the comments, Jeff. I have been using a config script call in Application.cfm to match the host header to a site in my tree, and set a request home node (as opposed to an application home node) which is used as the root for generating navigation, etc. The root->home node contains (eg) 404 and unregistered host handlers (incase a domain is added and not recognised) and utility-style objects that are aliased from the "real" site homes, but root->home isn't used other than that.
I'm now looking for a way of interacting with the navigation structure during a nav request, with the intention of: * Dealing with nav/objectIds from a different home gracefully, instead of displaying the object in the wrong skin and without credit to the correct home site * Inheriting settings (eg, banner image) down the tree, probably in a manner similar to CSS inheritance / overrides (very nifty) I'm really not sure where to hook in to Farcry to achieve this - the further into processing (eg, as part of a display) the better for manipulation, but at the expense of the speed (especially where a redirect is required) from earlier on. It doesn't seem right to make validation calls in the (currently) dmHeader.cfm, or in a display, but I can't see where would be better. I guess I'm just too green to know what my options are! Any suggestions appreciated ;) Chris -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Coughlin Sent: Friday, 21 January 2005 5:01 AM To: FarCry Developers Subject: [farcry-dev] Re: Multi-Tree Farcry Instance? Chris Bauer wrote: > I had done that, with > > Root > -home > -homeCry > -homeCryDev > > Without changing anything else, assuming that I could view the default > farcry (home) after an app refresh. The site ended up just outputting the > DOCTYPE header, and nothing after that. If I used Preview from the admin, it > went as far as to apply CSS and part of 'containerhead' depending on the > node (homeCry, HomeCryDev have cascading styles), but failed to get to the > HTML object. Perhaps I had a done something else bad? I'll try again! I am working on something similar (a site planned to be released in a couple weeks). This client wanted different locations (each has their own site and stylesheets, but a lot of dynamic information is shared amongst the iste like News & Events). I did mine like: home basic.css Advanced.css Print.css -Location1_homepage homepage.css (not used on any descendents) location1Colors.css -Location2_homepage homepage.css (not used on any descendents) location1Colors.css -Location3_homepage etc... Then when I have shared static content (say Privacy Policy in the footer) I make that page in root-utility (and give it an alias) and I place all of the static content in there. To navigate to this new page I make a "Privacy Policy" navigation node somewhere under my location_home (for each site) and use a symbolic link to point to the alias in the utility-Privacy Policy. In the end I have one content spot for the shared static content and I get the page to think it still resides in the site I came from (thus keeping stylesheets etc). By the way. In order to know which site I am under I created a CFC that gets info like my site's homepage alias name and more. I'd share it, but its likely too customized. -Jeff C. --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
