Hi again, Especially if you suspect that the nesting of your folders may change, this is is an excellent solution, and not necessarily either / or, as your example illustrates. Your example also shows that you do have to deal with calling the property as a <dtml-var> at every anchor, which you can just skip when you have a stable site that let's you adopt a "site relative" convention. I don't have a clue as to the "cost" of each little <dtml-var>, in terms of performance, and overall load on Zope, but I always figure no load at all is best, whenever you can swing it! Later, Jerry S. At 12:46 PM 1/31/00 +1000, you wrote:
+----[ Jerry Spicklemire ]--------------------------------------------- | Just to second Evan's motion, "site relative" links will make it much | easier to move the Zope pieces you're building to another Zope instance, if | and when the time comes. It's pretty painless to simply "Export" a | subfolder, and then "Import" into another Zope, knowing that everything | will still work, even though the DNS address, and name (alias), of the host | has changed.
Why not set a top level property that has the http://hostname/basefolder location in it.
All your URLS would become
<a href="<dtml-var BASELOCATION>/relativefolder">Blah</a>
Move locations, change the property -- everything works.
If you don't set it everything becomes relative to the root.
-- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|