Woohoo!

Worked like a charm... Thanks Jon!

(Robert - if I were a brave soul and used Linux, the symbolic links were my
first thought... But you're right - it won't work on Windows. Can't WAIT to
switch over to Witango 5 on one of them fancy new Xserve boxes!)

(Scott - this is what I was looking for to share a common folder of TCF
files across multiple websites... Very good trick indeed.)

Thanks again everyone!

Jason

On 5/21/02 7:50 AM, "Jon Grieve" <[EMAIL PROTECTED]> wrote:

> Jason,
> 
> I've certainly used "../common/TCF/Objects" kind of thing in the past.  So,
> that takes the<@WEBROOT> and steps up a folder and into a shared one.  From
> t4server.ini, I have:
> CUSTOMTAGSPATH=C:\\PVSW\\Tango2000\\Configuration\\CustomTags
> TCFSEARCHPATH=<@APPFILEPATH>;<@CLASSFILEPATH>;/Tango2000/TCF/;../CustomTags/
> Objects/
> 
> I have Custom Tags on a per-site basis, in that I don't want to load them in
> a global/system-wide scope (for naming reasons).  To achieve this, I first
> created a Witango Domain for the site:
> 
> domains.ini:
> --
> [Domains]
> jongrieve.net=
> 
> [jongrieve.net]
> 1=jongrieve.net
> 2=www.jongrieve.net
> 
> Next, I created a Witango Application for that domain:
> 
> applications.ini:
> --
> [Applications]
> jongrieve.net=
> 
> [jongrieve.net]
> DOMAIN=jongrieve.net
> PATH=/
> CUSTOMTAGSPATH=/wherever/jongrieve.net/CustomTags/Defs/
> 
> Note the undocumented CUSTOMTAGSPATH for the Application.  I'll throw in at
> this point that I don't use config.taf for this stuff; I manually edit the
> .ini files.
> 
> So, when the jongrieve.net Domain and Application are initialised, it finds
> the Custom Tag definitions (XML files) in the CUSTOMTAGSPATH path.  When it
> tries to create an instance of those objects, it uses the
> "../CustomTags/Objects/" part of system$TCFSEARCHPATH to load the object.
> 
> Hope this helps.
> 
> Jon
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Jason Pamental [mailto:[EMAIL PROTECTED]]
> Sent: 21 May 2002 12:27
> To: Multiple recipients of list witango-talk
> Subject: Re: Witango-Talk: Tcfsearchpath
> 
> 
> This is exacty the problem... I've been trying to figure out how to share a
> common directory of tcf's. The odd thing is that the server will prepend the
> tcfsearchpath (set either in the ini file or in the taf with an assign
> action) with the actual full path to the webroot, so even trying a virtual
> directory won't work because the full path still doesn't work. (no symbolic
> links that work the same as Unix on Windows)
> 
> Thanks,
> 
> Jason
> 
> On 5/21/02 1:03 AM, "Robert Garcia" <[EMAIL PROTECTED]> wrote:
> 
>> The TCFSearchPath variable is always relative to the webroot of the taf
> you
>> are running. Unless there is a way to change that. So there should be no
>> need for <@webroot>. I changed my setting to:
>> 
>> 
> TCFSEARCHPATH=<@appfilepath>;<@classfilepath>;/Tango2000/tcf/;/tcfs/;/appfil
>> es/tcfs/;
>> 
>> All paths that start with "/" are relative to the webroot. If I want to
>> instantiate an object instance and the tcf is in a different place, just
> add
>> this before you create the instance:
>> 
>> <@assign local$TCFSEARCHPATH "/ThePath/ToYourTCF/">
>> 
>> And for this one instance, tango will look in this path.
>> 
>> Hope this helps.

-- 
____________________________________________________________________

Jason Pamental, President                   [EMAIL PROTECTED]

Bathysphere Digital Media Services, Inc.   http://bathyspheredms.com
____________________________________________________________________

Tel: 401.490.6830      Fax: 401.490.6831
________________________________________

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to