You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Jörn Nettingsmeier <po...@uni-duisburg.de> on 2006/09/22 08:49:24 UTC
how does bxe_xpath work?
hi!
since the last changes in bxe preprocessing, bxe has been broken in my
custom publication. i get an empty usecase view. and there my debugging
skills end, because the rest is deep javascript magic. :(
it looks like the publication is now responsible to add an element with
a bxe_xpath attribute - correct?
the default publication defines one in xslt/lenya-header.xsl, but it
seems nothing ever calls into that file... can anyone explain?
i've read the bxe wiki, and it seems i need to give an xpath to the
element i want to be editable, which in my case would be
/html/body/div[@id='body']... however if i add that to a div on my page,
nothing happens... any hints welcome.
jörn
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
SOLVED: how does bxe_xpath work?
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Jörn Nettingsmeier wrote:
>
> [...]
>
>> it looks like the publication is now responsible to add an element with
>> a bxe_xpath attribute - correct?
>
> Hmmm, actually that should be deliviered by the resource type.
>
>> the default publication defines one in xslt/lenya-header.xsl, but it
>> seems nothing ever calls into that file... can anyone explain?
>
> Indeed, it seems to be orphaned. The content is obsolete
> (it refers to old meta data). I'm afraid it won't be easy to edit
> the dc:title in BXE with the new externalized meta data. But IMO
> that's not really necessary.
>
>> i've read the bxe wiki, and it seems i need to give an xpath to the
>> element i want to be editable, which in my case would be
>> /html/body/div[@id='body']... however if i add that to a div on my page,
>> nothing happens... any hints welcome.
i found the problem, and it was indeed my own fault.
it seems that there are access control restrictions for module resources
as well. that means you need a subdir "modules" in
yourpub/config/ac/policies with a <world><role id="visit
method="grant"/></world> rule in it.
after adding it, i got my bxe back.
> Would you mind filing a bug?
well, the main issue was clearly my fault - i missed the addition of
modules ac. as to the orphaned file, i'll do some testing and then
remove it if nothing breaks.
regards,
jörn
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: how does bxe_xpath work?
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
[...]
> it looks like the publication is now responsible to add an element with
> a bxe_xpath attribute - correct?
Hmmm, actually that should be deliviered by the resource type.
> the default publication defines one in xslt/lenya-header.xsl, but it
> seems nothing ever calls into that file... can anyone explain?
Indeed, it seems to be orphaned. The content is obsolete
(it refers to old meta data). I'm afraid it won't be easy to edit
the dc:title in BXE with the new externalized meta data. But IMO
that's not really necessary.
> i've read the bxe wiki, and it seems i need to give an xpath to the
> element i want to be editable, which in my case would be
> /html/body/div[@id='body']... however if i add that to a div on my page,
> nothing happens... any hints welcome.
Would you mind filing a bug?
Thanks for reporting!
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: how does bxe_xpath work?
Posted by Michael Wohlfart <mi...@wohlfart.net>.
Hi Jörn,
the following code worked for me some time ago in lenya 1.2.4, not sure
if $rendertype still used in 1.4 :-/
<xsl:template match="/xhtml:html">
<xsl:copy-of select="lenya:meta"/>
<div id="body">
<xsl:if test="$rendertype = 'edit'">
<xsl:attribute name="bxe_xpath">/xhtml:html/xhtml:body</xsl:attribute>
</xsl:if>
<xsl:apply-templates select="xhtml:body/node()"/>
</div>
</xsl:template>
/html/body/div[@id='body'] seemes logical for me too, but for some reason
it didn't work. BXE really has a lot of magic...
michael
Jörn Nettingsmeier wrote:
> hi!
>
>
> since the last changes in bxe preprocessing, bxe has been broken in my
> custom publication. i get an empty usecase view. and there my debugging
> skills end, because the rest is deep javascript magic. :(
>
> it looks like the publication is now responsible to add an element with
> a bxe_xpath attribute - correct?
>
> the default publication defines one in xslt/lenya-header.xsl, but it
> seems nothing ever calls into that file... can anyone explain?
>
> i've read the bxe wiki, and it seems i need to give an xpath to the
> element i want to be editable, which in my case would be
> /html/body/div[@id='body']... however if i add that to a div on my page,
> nothing happens... any hints welcome.
>
> jörn
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org