Hi Jason.
I've noticed that PostAuthHooks can be fairly temperamental.
You should add to the top of your postauthhook file:
use strict;
use warnings;
Don't forget to do
perl -c "file.pl"
to syntax check it.
One of the reasons I've noticed for silent failures on PostAuthHooks are
undeclared variables. If you've added a new variable somewhere, or used
a temporary variable without a my declaration, that could be it.
use strict && use warnings are always a good idea.
Hope this helps.
Cheers,
Robert Thomson.
begin Separovic, Jason quotation:
> I had radiator working with my PostAuthHook just how I wanted.
> Then I made some changes to the PostAuthHook. All I did (I think?) was
> create a new user in my database and then I updated the new
> username/password in the config files. Now My PostAuthHook does not work.
> And I'm at a loss to realise why??
>
> Here is an Accounting Request that should be inserted into my database
> through the PostAuthHook.
> But now the Hook is not even being called. I'm pretty confident in saying
> that because I added a 'write to file' at the beginning of the hook to test
> it. But to no success.
>
> I noticed some talk about a patch for the PostAuthHook but I'm not sure if I
> need it.
> Weird.
> It was working...
> Now it's not.
>
> Help!
>
> I'm using Radiator 2.17.1
--
Vundan lokon protektis, alian difektis.
-- L.L. Zamenhof, "Proverbaro Esperanta" (1905)
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
