On Friday 10 January 2003 16:16, J�rg Walter wrote:
> sub password_matches__true___open {

> sub password_matches__true {

> auth:true, obviously. Btw, in "password_matches__true___open" that's
> one underscore for the "-" in "password-matches", two underscores for
> matching auth:true only below auth:password-matches, and then three
> to specify the open-event.

Uh, I'm quite confused now... :-) This is supposed to be the other way 
around, isn't it...? That you have ___ for true, and __ for open...? 

You see, the really weird thing is that I could swear it worked _once_ 
with having it the other way around (like you wrote), but after that 
single time, I got errors like this:
[Sun Jan 12 18:37:16 2003] [error] [client 127.0.0.1] [AxKit] 
[Backtrace] Parse of '/var/www/passwdtest.xsp' failed: invalid tag: 
true (namespace: http://www.creITve.de/2002/XSP/Auth, package 
AxKit::XSP::Auth::Handlers, parents password-matches, password-matches) 
at /usr/lib/perl5/Apache/AxKit/Language/XSP/SimpleTaglib.pm line 450, 
<_GEN_3> line 1.

But I may have been hallusinating... :-) 

Anyway, the style cache is also confusing me. Sometimes, when I'm having 
trouble and nothing seems to go my way, I get this feeling that things 
are pulled from cache rather than from my new changes. For example, 
I've had times where I get 500-errors when I hit reload, but the 6th 
time I hit reload, I get the XSP-page unprocessed... How can I control 
the style cache? Is there any way I can disable it entirely (obviously, 
it is a great feature that will be of great importance when I go to 
production, but now it is mostly giving me headaches...) I've symlinked 
..xmlstyle/ to /dev/null, but that may have side-effects, I guess. 

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to