I have been manually purging the entire cache whenever I made updates, but was looking for an automated, selective purge to integrate with a perl script I use for third parties to push their sites (via rsync) to a production server. So instead of having my purge.taf's in the clients' web sites, I'll move it to a directory to which they don't have access, so I can include the password in the file and then do a full cache purge..
Crude. On Monday, February 14, 2005, at 08:53 PM, Robert Shubert wrote:
In 5.0, purgecache is a little weird. The applications are stored in the
cache based on domain scope, not application scope, but that's not
brought out in the purgecache tag, so it doesn't do you much good. The
path is literally just a path, so if you put all your TCFs in /TCF, and
you wanted to just purge them, you could with the path attribute. Again,
not an entirely useful function, but might help some people. I'm not
sure if the application path will match here, as I don't support
application scope on my servers. I just set the password and purge the
entire cache. Crude, but it doesn't cause me any troubles - although
others on the list have said that purging the cache can cause
instability.
What I really want to say here, however, is that @PURGECACHE in 5.5 acts
completely different, and without getting into the details, it's finally
fixed. Since you can now specify a domain scope, you can now target a
website's worth of files (the path now makes more sense as well, to
drill down to certain level of a website).
Robert
-----Original Message----- From: Bill Conlon [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 5:25 PM To: Witango-Talk Subject: Witango-Talk: purging cache
I want to purge a application's files from the cache. (PATH is defined in applications.ini).
But <@PURGECACHE> returns:
An error occurred while processing your request:
File: purgecache.taf Position: Results Class: Internal Main Error Number: -27
Invalid Password detected. Insufficient security privileges
Yet, the manual indicates that user$configpasswd only needs to be set if the optional PATH attribute is used in <@PURGECACHE>. Do I need to add CONFIGPASSWD to the relevant stanza in applications.ini, and then set user$configpasswd in prior to calling <@PURGECACHE>?
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
