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ürgen Ragaller <ra...@null-oder-eins.ch> on 2006/09/01 15:11:50 UTC
1.4-dev Custom xhtml Sample Page
Hi all!
I'm trying to customize the xthml Sample Page for my publication. In
1.4 the sample page is nicely packaged within the xthml module. Is
there an overwrite/fallback way to have a publication specific xthml
sample?
Help is appreciated!
Jürgen Ragaller
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: 1.4-dev Custom xhtml Sample Page
Posted by Jürgen Ragaller <ra...@null-oder-eins.ch>.
Am Sep 1, 2006 um 18:55 schrieb Jörn Nettingsmeier:
> Jürgen Ragaller wrote:
>> Hi all!
>> I'm trying to customize the xthml Sample Page for my publication.
>> In 1.4 the sample page is nicely packaged within the xthml module.
>> Is there an overwrite/fallback way to have a publication specific
>> xthml sample?
>
> [stage lights, curtain.]
> [enter fallback, to pompous music.]
>
> in your publication's root directory, create a directory tree
> "lenya/modules/xhtml/samples/"
> in there, place a file xhtml.xml with your desired sample content.
> you should probably base it on the one in the core.
>
> in all sitemaps that come with lenya, most resources should be
> addressed with the fallback:// uri, i.e. the xhtml module sitemap
> will access the sample as fallback://lenya/modules/xhtml/samples/
> xhtml.xml instead of "context://lenya/modules/xhtml/...". the
> fallback source resolver will now first look in your publication
> for this path and file, then in the template, the template's
> template, ..., and finally in the core.
> using this mechanism, you can selectively customize stuff without
> having to rewrite entire modules. neato :)
>
> the general technique is to mimic the part of the directory tree
> from build/lenya/webapp you want to override. (again, this depends
> on the core sitemaps using fallback:// for the particular
> resource). so if it does not work, check the sitemaps and possibly
> file a bug.
[drumroll, horns - audience cheers. a big warm applause for the author]
Thank You, Jörn - this was very helpful.
Jürgen
>
> best,
>
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: 1.4-dev Custom xhtml Sample Page
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Jürgen Ragaller wrote:
> Hi all!
>
>
> I'm trying to customize the xthml Sample Page for my publication. In 1.4
> the sample page is nicely packaged within the xthml module. Is there an
> overwrite/fallback way to have a publication specific xthml sample?
[stage lights, curtain.]
[enter fallback, to pompous music.]
in your publication's root directory, create a directory tree
"lenya/modules/xhtml/samples/"
in there, place a file xhtml.xml with your desired sample content. you
should probably base it on the one in the core.
in all sitemaps that come with lenya, most resources should be addressed
with the fallback:// uri, i.e. the xhtml module sitemap will access the
sample as fallback://lenya/modules/xhtml/samples/xhtml.xml instead of
"context://lenya/modules/xhtml/...". the fallback source resolver will
now first look in your publication for this path and file, then in the
template, the template's template, ..., and finally in the core.
using this mechanism, you can selectively customize stuff without having
to rewrite entire modules. neato :)
the general technique is to mimic the part of the directory tree from
build/lenya/webapp you want to override. (again, this depends on the
core sitemaps using fallback:// for the particular resource). so if it
does not work, check the sitemaps and possibly file a bug.
best,
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