[imp] Auth::authenticate() login problems

[Chris Miller]

Many thanks Chuck,

My final question was

"And finally, on correct login and display of a block
, on the occurrence of any interaction with  
 the block that should fire the horde portal, how do I firstly adjust  
 the links to reflect the horde url ?"

I will reword!

On correct login to horde, with a call to a particular block which will dump
html into a non horde page, how do I adjust the <a href="..."> links to
reflect where the page is?

i.e. an example would be, I have a file stuffwithhorde.php in
www.mydomain.com/admin/stuffwithhorde.php, or in the 
/admin/ folder of my mydomain.com root directory (perhaps if virtual
hosting). Indeed this path might even be the root directory itself, or
further up than one level. Horde, as must installs are, is located at
/horde/ (and can be an alias for several different hosts). As long as I can
change the links that are output to reflect that they should prefix with
/horde/ then I can use it anywhere.

So when a user clicks horde content, it should take the person to the
correct page, or operation etc.

Also a quick note. Is it advisable to use the HEAD from the CVS whilst
learning these steps and interacting, or is a stable branch good enough ?

Regards

Chris



-----Original Message-----
From: imp-bounces at lists.horde.org [mailto:imp-bounces at lists.horde.org] On
Behalf Of Chuck Hagenbuch
Sent: 15 December 2006 04:12
To: imp at lists.horde.org
Subject: Re: [imp] Auth::authenticate() login problems

Quoting Chris Miller <chris at integratedventures.co.uk>:

> I realise I can use the registry object to list operations available to
me,
> and particularly interesting is 'horde/blockContent'
>
> I have worked out that
>
> $registry->call('horde/blockContent', *)
>
> Can provide parts of particular applications in html, this is a fantastic
> feature! I have also assumed that by trawling the API I can discover which
> block contents can be used by seeing which implementations of Horde::Block
> the application supplies.
>
> Are these the only such calls one can use (I assume yes)?

I'm not sure what the question is. horde/blocks will return a list of  
all available blocks.

> If there are parameters for this call, how does one deduce what these can
> be. In your example in the wiki
>
> $registry->call('horde/blockContent', array('kronolith', 'month',
> array('calendar' => 'jan')));
>
> The class I assume to be used here is Horde_Block_Kronolith_month defined
in
> month.php

Yup.

> How is it possible to deduce the array('calendar' => 'jan') param is
> available ?

There isn't really introspection through API calls for this, but if  
you look at that file (month.php as above), you'll see a _params()  
method that returns the list of expected parameters, human names,  
type, possible values for enums, etc.

> Additionally, the login discussed above, by providing
> $authenticated = auth->authenticate('username', array('password' =>
> 'realpassword'), true);
>
> This logs into a session until a horde logout occurs ?

Yes.

> And finally, on correct login to an application

You log in to Horde, not to specific applications.

> and display of a block, on the occurrence of any interaction with  
> the block that should fire the horde portal, how do I firstly adjust  
> the links to reflect the horde url ?

I'm sorry, I don't follow this question.

> I believe being able to understand this stage should make horde very
usable
> to me, and as previously suggested I can collect my experiences into a
> possibly useful document for the wiki or something

That'd be great!

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris
-- 
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscribe at lists.horde.org

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.17/583 - Release Date: 12/12/2006
16:45
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.17/583 - Release Date: 12/12/2006
16:45