Scott Talsma wrote:
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.
This is certainly the best approach. Especially with things like custom tags. There is absolutely no harm creating your own project specific custom tags and referencing these rather than the core tags. things are kind of designed that way. Changing core tags is risky as these may well evolve over time.
-- geoff http://www.daemon.com.au/ -- Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering. http://www.mailguard.com.au/mg
