I think Matt was just saying that / already IS the webroot in both the
web (and the root in a *nix file system). You don't really need a named
param to define a immutable constant in this case.
And correct on your point below re includes: It's the /file/ that's
reusable - not always the /path to it/.
So you can just be literal - and relative - with your include template
paths. You could use a variable within a part of it - if you want. But
If you really keep moving it; then either you've probably got a function
there - or some more thinking left to do (before coding) anyway.
Al
On 5/29/2012 12:10 PM, Jason King wrote:
Honestly,
I really don't see a reason why I couldn't just use relative paths.
But if I have a specific document that I need to include very often,
but it's included from various folders from various distances from the
webroot, I have to specifiy each instance of the include differently
each time. Not a big deal, but I'm just looking for a way to have it
declared in a 'one size fits all' way.
Matt earlier asked if my application didn't understand 'webroot'. Is
that a reserved word variable that points back to the webroot?
<cfinclude template="/webroot/admin/google/ad.cfm"> ??
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
