Not sure I'm totally understanding problem, but sounds like you may be trying to use some settings that apply to all the *sites*, such as for a parent business. Since you are defining application as unique to each site, don't think you can mix parent and child in application variables. In this dynamically-set application, all is tied to the BusinessID. To accomplish what I think you're trying to do, I'd suggest you include your *common* variables as part of the application. In a similar situation, I do the followinig: 1. Have a script on application.cfm to get the appropriate BusinessID. 2. Run a series of queries and/or other routines to set up an application structure for site settings. This can include some portions that are global (will be same for all sites under this parent app) and some/most that will be unique to the called site. (I've not done this, but guess you could have a couple levels: application.stSettings.Global and application.stSettings.Specific, such as application.stSettings.Global.InfoEmail; application.stSettings.Specific.BusEmail) (I even cache some of the larger queries so the routine is faster the few times it is needed.) 3. In application.cfm, if the application.stSettings exists and is a structure, duplicate the application.stSettings into request scope. If not, run the earlier #2 routine and duplicate to request scope. 4. All the queries in establishing the settings structure most likely will only be run once. After that, since the application structure does exist, what is run with each page call--I think--is just the duplication of that app structure to request. 5. Note: need a method that will rerun the template that sets the application structure anytime you change any of the global or site-specific information, so that app structure is always current. 6. Now all your settings variables are available on any page, called through the request.stSettings sturcture. "For info on how this site works, contact #request.stSettings.Global.InfoEmail#" "Contact MyBusiness at #request.stSettings.Specific.BusEmail#"
I've tried to extrapolate what I've done in something similar to what I think you're trying to do. Don't know that all is totally correct, but should get you on a workable road. As with most such things, there are probably several ways to accomplish the goal. I guess you could have two structures: one that is for the global stuff and one for the unique, but the global would still have to be tied to the specific site application. application/request.stGlobSets and application/request.stSpecificSets. Then on output you just call whichever applies. Seems though that makes sense just to make them all part of one settings structure. Hope this helps Keith ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
