cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Portal/Coplet-Behaviour
Date Wed, 07 Aug 2002 07:29:49 GMT
> -----Original Message-----
> From: u15603 [mailto:u15603@hs-harz.de]
> Sent: Tuesday, August 06, 2002 5:11 PM
> To: cocoon-users@xml.apache.org
> Subject: Portal/Coplet-Behaviour
> 
> 
> Hello,
> 
> we are trying to adapt the cocoon portal to our needs. But we 
> have some problems! In the 
> headline of the coplets cocoon does not "create" the buttons 
> delete,minimize/maximize 
> ... .  It is caused by the stylesheet portalHTML.xsl, because 
> there are case 
> distinctions. For instance for the customize-button the following:
> 
> <xsl:if test="configuration/customizable='true' and 
> (not(status/customize) or 
> status/customize='false')"> 
> 
> But when we read the session-context "portal" we can't find a tag 
> like <status>. 
> 
> When does cocoon set/write these tags?
> 
The <status> and <configuration> information for a coplet are stored
in the portal profile. Usually this is the coplet base profile where
all coplets are defined.

> Another problem is that we can't find a session-context that 
> contains the authentication 
> information. In which context is this stored? We can successfully 
> log into the portal.  
> 
The authentication information is stored in a session context called
"authentication".

Carsten

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message