Chris, Thanks. Thats along the lines of what I was thinking.. I wanted to post that out there in the event I was mission "something".. but this sounds like the most manageable way to do it. Thanks!
On Sep 23, 11:53 am, Chris Kent <[EMAIL PROTECTED]> wrote: > Chris, > > Let me first assume that you are using friendly URL’s. If so then > maybe the following will help you, it worked for me. > > On a page url.path would equal /go/sales/widgets/.... or /go/support/ > widgets/.... etc. > > <cfset section = listGetAt(url.path,2,"/")> will get either “sales” or > “support” depending on what page is being displayed. > > You can then use this in your container names to have a container for > sales to pull support content and vice versa. e.g. > <con:container label="#section#" defaultMirrorLabel="#section# > Container"> > > Dynamic container naming is very powerful. > > Chris. > > On Sep 23, 6:25 pm, Chris Roth <[EMAIL PROTECTED]> wrote: > > > > > Looking to get some ideas on using containers/rules. > > > I have "sales" and "support" nav nodes that are basically mirrors of > > eachother. in that that have the same "structure". For example, under > > sales there are product sections Widgets (A,B,C,D) Wodgets (A,B,C,D) > > Wadgets (A,B,C,D) and under support there would be resources specific > > to the products under Widgets, Wodgets, Wadgets. > > > I am usign a 3 column layout in both sections. > > > I'd like to have a shared container under "Widgets" sales that links > > to Widgets support and vice versa. And under support, I might have a > > container/rule that have popular "Widget" support links (dmfiles, > > dmhtmls ,etc). > > > What I would like to NOT do is have to have a displayPageWidgetSales, > > displayPageWidgetSupport since this would basically be giving me 6 > > displayPage templates that are all essintially the same wit hthe > > exception of the shared container resource. > > > My thinking is to try and dynamically assign the reflection for the > > container based on the navid. This, if I am thinking clearly would > > allow me to have a single displayPage webskin, and the containers > > could be managed from the web top using publishing rules specific to > > the container. > > > the displayPage webskin could have a second "generic" container for > > rules that might not apply across the board. > > > Anyone doing anything like this? Anyone have suggestions to achive the > > effect? maybe I am missing something thats easier?- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
