it now seems to work, the only problem left is how to reforce the login
dialog if "chancel" is pressed.
when i try to make a simple loop for ->authenticate() like:
$end = false;
while($end != true)
{
$result = $a->authenticate();
if ($result->isValid()) $end = true;
}
i never get the dialog login.
So my question is: where is the login dialog triggered in code and how
to solve the "chancel" use case ?
The complete code is inside a Controller Plugins /dispatchLoopStartup()/
method.
best regards,
Truppe Steven
till wrote:
> Hi,
>
> On 9/4/07, Truppe Steven <[EMAIL PROTECTED]> wrote:
>
>> Hello again,
>>
>> i have now setup a local apache server with xdebug, and here the example
>> is working without code changes !!
>>
>> The online version is located on a subdomain, the local copy is just a
>> virtualhost. Maybe the Http Adapter for digest authentication can't
>> handle subdomains ?
>>
>
> I don't know what difference it makes. I am rather guessing your
> problem is elsewhere. Mybe you can pastebin some code so people can
> help you.
>
>
>> With the local copy i FINALY get a successful login with the right
>> credentials.
>>
>> Are there other modules than "hash" that are needed for this to work
>> properly ?
>>
>
> I stumbled upon "hash" as well. I still believe that one of the
> advantages about distributing ZF using a PEAR channel would be proper
> dependency checking. Not just internally (so to speak package-wise)
> but also in relation to your PHP install. Because I did not have hash
> installed either and someone on the issue tracker claimed it was
> "common". ;-)
>
> Do you have your logs enabled and error_reporting set to E_ALL and
> E_STRICT? Because if there is an error, notice or warning it would end
> up there - if you don't see anything on the page while you load it. A
> fatal error is usually indicating a missing module.
>
> Cheers,
> Till
>
>