News (and other non dmHTML content) can have a default location set for it relatively easily by changing the value of request.navid at the top of the display template.
<cfparam name="application.navid.news" default="application.navid.home"> <cfset request.navid=application.navid.news>
*ALL* news content will use this location. You can certainly get around this too... but that's a lesson for another day.
This was very helpful Geoff, thanks.
So whats the best way to dynamically know what area to go to? (I'm refering to your last sentence). I have several branches in the site tree that have their own news page. They share the same news info (so I don't need to worry about having different content for different areas), however they use their own stylesheets (dmCSS).
I can only think of two ways (both I don't like):
1. Grab the http_referrer and find out what branch their objectid came from (would work, but it'd be messy).
2. Use custom webskins (only thing different would be that <cfparam> value). This would work also, but it wouldn't be scalable. The users would have to rely on a developer to create a new template file for each branch (there are many). Also if the template/layout ever changed the developer might have to consider editing all of the templates (I know there are ways around this one, but still this option is too messy).
There's got to be a cleaner/ more scalable way to write this. Any ideas?
-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/
