Hi Bill, Welcome to the group.
You are very close with your solutions. You can have the code hardcoded in your foundation content classes, but with this method, if you have n foundation content classes, and you need to change the code, then you have to change it n times. Hence, this is definitely not a best practice and would get you red flag in OpenText's health check audit. Since contact us module is a common module, adding the code there is perfect because you will have a central place to maintain the code. Like you said, not elegant because now you are mixing code of different purposes in a single content class/page. But you did have the right idea, what if you create a con_google_analytics container in all foundation content classes, create a new content class that has the google analytics code, create a page instance from the google analytics content class, use the plugin Retroactive References 2 to retro actively reference con_google_analytics in all foundation page instances to the google analytics page. Plugin here: http://www.solutionexchange.info/Retroactive-References-2.htm If you need more information as a guide on what I am talking about, take a look at how your site header or footer is handled in the project structure. Good luck, -Jian On Oct 19, 6:42 pm, Bill Bernat <[email protected]> wrote: > I need to place analytics code on our site. I can easiliy throw it > into a contact us container that appears on every page, but that's > kind of inelegent. > > Is there a standard/best practice way to do this? I'm fairly new to > RedDot, just inherited a site to administer. > > Thanks, > -billb -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" 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/reddot-cms-users?hl=en.
