The only problem w/doing so is that when the next update comes out, you will have to be selective about how you overwrite the farcry_core.  Additionally, the backend may use those files as well (now or in the future).  In general, the rule is "Do not mess w/the core."
 
I assume that you need to change how the links are written in your templates (display methods located in farcry_projects/webskin).  I would simply copy the two files to webskin/includes (or for that matter, webskin/myDirectory) and modify them there.  Then you can call them all you want from the front-end, w/o endangering your upgrade path.  I did something similar w/copyTree a while back, and that strategy worked fine.
 
Scott Talsma
CTO
echo•eleven
404.845.3458
 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bash (sent by Nabble.com)
Sent: Wednesday, January 25, 2006 3:07 PM
To: [email protected]
Subject: [farcry-dev] Modifying core webskin files

What are options/implications for modifying the webskin files in the farcry_core? I need to change the way links are written in the genericNav.cfm and relatedLinks.cfm or secondaryNav.cfm. Is there a way to override these files or do I need to modify the files themselves?

View this message in context: Modifying core webskin files
Sent from the FarCry - Dev forum at Nabble.com.

Reply via email to