You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lenya.apache.org by gr...@apache.org on 2005/05/16 01:56:55 UTC
svn commit: r170282 [1/2] - in /lenya/docu/src/documentation/content/xdocs:
./ 1_2_x/components/editors/ 1_2_x/components/workflow/ 1_2_x/how-to/
1_2_x/misc/ 1_4/reference/ community/
Author: gregor
Date: Sun May 15 16:56:54 2005
New Revision: 170282
URL: http://svn.apache.org/viewcvs?rev=170282&view=rev
Log:
Made new documentation valid forrest documents.
Removed:
lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/introduction.xml
Modified:
lenya/docu/src/documentation/content/xdocs/1_2_x/components/editors/kupu.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/implementation.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/state-machine.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_menus.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_screens.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/custom_resourcetype.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/deploy_publication.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/external_data.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/faq.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/ldap_authentication.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/look_and_feel.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_mime_type.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_publication.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/search.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/site_navigation.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/using_pictures.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/misc/reserved_names.xml
lenya/docu/src/documentation/content/xdocs/1_2_x/misc/unittests.xml
lenya/docu/src/documentation/content/xdocs/1_4/reference/lenya-sitemaps.xml
lenya/docu/src/documentation/content/xdocs/community/translations.xml
lenya/docu/src/documentation/content/xdocs/index.xml
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/components/editors/kupu.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/components/editors/kupu.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/components/editors/kupu.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/components/editors/kupu.xml Sun May 15 16:56:54 2005
@@ -38,7 +38,7 @@
</section><section><title id="head-cb7dd8a2b1dc471e0805416826a330e77b1cce07">What integrating an editor is all about</title>
<p>From the user's perspective using an editor in Lenya works like this: </p>
-<ol type="1">
+<ol>
<li><p>Navigate to the item that is to be edited </p>
</li>
<li><p>Click on a link to start the editing process (mostly from a pull-down menu, but there are other options) </p>
@@ -56,7 +56,7 @@
As simple as that sounds, there is a number of things Lenya has to go through. </p>
<p>Between Step 2. and 3. (the user clicking on 'Edit' and the editor showing up) Lenya has to </p>
-<ol type="1">
+<ol>
<li><p>Make sure the editor is installed at all </p>
</li>
<li><p>Determine the file to be edited </p>
@@ -67,7 +67,7 @@
</li>
</ol>
<p>Between Step 3. and 4. (Edit and Save) Lenya has to </p>
-<ol type="1">
+<ol>
<li><p>Make sure the file is still checked out so it can be edited </p>
</li>
@@ -83,13 +83,11 @@
<p><em>Note: Kupu allows the user to Save in between and continue editing. This is achieved by using HTTP POST operations. Thus Lenya needs to be prepared to
receive multiple updates of the same page and save it before the user might click on 'Exit and Save' so that Step 5 (Display the changed page) is finally triggered.</em> </p>
-<h3 id="head-e5a2711688441b7644fbdb11a61307c04fbf2061">The Kupu usecase pipeline in detail</h3>
+</section><section><title id="head-e5a2711688441b7644fbdb11a61307c04fbf2061">The Kupu usecase pipeline in detail</title>
+<section><title id="head-42ce962db03bd610fa943bc40b509ba6985810fd">step="open"</title>
-</section><section><title id="head-42ce962db03bd610fa943bc40b509ba6985810fd">step="open"</title>
-
-
-<pre>
+<source>
<map:match pattern="kupu" type="usecase">
<map:match pattern="open" type="step">
<map:match pattern="*/authoring/**.html">
@@ -129,12 +127,12 @@
</map:match>
</map:match>
-</pre>
+</source>
</section><section><title id="head-f6ed65665fa1e56a5371d0ab376effe42403dfae">step="content"</title>
-<pre>
+<source>
<map:match pattern="content" type="step">
<map:match pattern="*/authoring/**.html">
<map:generate src="pubs/{1}/content/authoring/{page-envelope:document-path}"/>
@@ -147,12 +145,12 @@
</map:match>
</map:match>
-</pre>
+</source>
</section><section><title id="head-211e1aede1d0c03aa8411a1d19a43d3f5d18ccc9">step="save"</title>
-<pre>
+<source>
<map:match pattern="save" type="step">
<map:select type="request-method">
<map:when test="PUT">
@@ -211,6 +209,6 @@
</map:select>
</map:match>
-</pre></section>
+</source></section></section>
</body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/implementation.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/implementation.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/implementation.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/implementation.xml Sun May 15 16:56:54 2005
@@ -28,44 +28,31 @@
<section><title>Important Classes</title>
-<p><tt>org.apache.lenya.workflow</tt> The actual workflow API. It defines the workflow model. </p>
+<p><em>org.apache.lenya.workflow</em> The actual workflow API. It defines the workflow model. </p>
<ul>
-<li><p> <strong>Workflow</strong> - A workflow object describes a workflow schema. </p>
-</li>
-<li><p> <strong>WorkflowInstance</strong> - A workflow instance. </p>
-
-</li>
-<li><p> <strong>Situation</strong> - The environment of the workflow before the invocation of an event. </p>
-</li>
+<li><strong>Workflow</strong> - A workflow object describes a workflow schema.</li>
+<li><strong>WorkflowInstance</strong> - A workflow instance.</li>
+<li> <strong>Situation</strong> - The environment of the workflow before the invocation of an event.</li>
</ul>
-<p><tt>org.apache.lenya.workflow.impl</tt> A basic abstract implementation of the API. </p>
+<p><em>org.apache.lenya.workflow.impl</em> A basic abstract implementation of the API. </p>
<ul>
-<li><p> <strong>WorkflowInstanceImpl</strong> - Basic implementation of a workflow instance. </p>
-
-</li>
-<li><p> <strong>History</strong> - The history of a workflow instance. Use a history object to restore </p>
-</li>
+<li> <strong>WorkflowInstanceImpl</strong> - Basic implementation of a workflow instance. </li>
+<li> <strong>History</strong> - The history of a workflow instance. Use a history object to restore</li>
</ul>
<p>the state of a workflow instance. </p>
-<p><tt>org.apache.lenya.cms.workflow</tt> Some CMS-specific workflow implementation classes. </p>
+<p><em>org.apache.lenya.cms.workflow</em> Some CMS-specific workflow implementation classes. </p>
<ul>
-<li><p> <strong>WorkflowFactory</strong> - A factory to build all workflow-related objects. </p>
-
-</li>
-<li><p> <strong>WorkflowDocument</strong> - A workflow instance wrapper for a CMS document. </p>
-</li>
-<li><p> <strong>CMSHistory</strong> - CMS-specific workflow instance history. </p>
-</li>
-<li><p> <strong>CMSSituation</strong> - CMS-specific environment situation. </p>
-
-</li>
+<li> <strong>WorkflowFactory</strong> - A factory to build all workflow-related objects. </li>
+<li> <strong>WorkflowDocument</strong> - A workflow instance wrapper for a CMS document. </li>
+<li> <strong>CMSHistory</strong> - CMS-specific workflow instance history. </li>
+<li> <strong>CMSSituation</strong> - CMS-specific environment situation. </li>
</ul>
</section><section><title id="head-2d1540f5c092fb4a2a534c9f988b419503a58bfc">Obtaining Workflow Instance and Situation Objects</title>
-<p>Use the <tt>WorkflowFactory</tt> to obtain workflow-related objects: </p>
+<p>Use the <em>WorkflowFactory</em> to obtain workflow-related objects: </p>
-<pre>
+<source>
Document document = new DefaultDocument(
publication, pageEnvelope.getDocumentId());
@@ -86,7 +73,7 @@
...
}
-</pre></section>
+</source></section>
</body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/state-machine.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/state-machine.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/state-machine.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/components/workflow/state-machine.xml Sun May 15 16:56:54 2005
@@ -51,7 +51,7 @@
<li><p> <strong>T</strong> is a set of transitions: <strong>T</strong> subseteq <strong>E</strong> x <strong>S</strong> --> <strong>S</strong> x <strong>CS</strong> x <strong>AS</strong> </p>
<ul>
-<li style="list-style-type:none"><p>with </p>
+<li><p>with </p>
</li>
<li><p> <strong>CS</strong> subseteq <strong>C</strong> </p>
</li>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_menus.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_menus.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_menus.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_menus.xml Sun May 15 16:56:54 2005
@@ -37,25 +37,21 @@
<p>Make sure you read that before continuing reading this page here! </p>
<p>Unfortunately the picture on the page mentioned above is a bit misleading. You might think that "Usecases" and "Workflow" steps in read in the right part of the picture refer to XSLT stylesheets which are applied using the XSLT transformer. This is not the case! They are own transformers implemted directly in the Lenya Java layer: </p>
-<pre>
+<source>
<map:transformer name="workflowmenu" logger="lenya.sitemap.transformer.workflowmenu" src="org.apache.lenya.cms.cocoon.transformation.WorkflowMenuTransformer"/>
<map:transformer name="usecasemenu" logger="lenya.sitemap.transformer.usecasemenu" src="org.apache.lenya.cms.cocoon.transformation.UsecaseMenuTransformer"/>
-
-</pre>
+</source>
<p>Nevertheless they do exactly what is described in the picture: They disable menu options if they are not accessible because </p>
<ul>
-<li><p> executing the usecase requires a role which the user belonging to the current session is lacking or </p>
-</li>
-<li><p> the current workflow state of the document forbidds the usecase </p>
-</li>
+<li><p> executing the usecase requires a role which the user belonging to the current session is lacking or </p></li>
+<li><p> the current workflow state of the document forbidds the usecase </p></li>
</ul>
-
</section><section><title id="head-f06da7765bdcb4fdb7ca94cedada41bafeee1d5b">Introducing a new menu option</title>
<p>First of all, before you start adding a new menu option to the CMS menus, ask yourself what usecase should be linked to that menu option and if the usecase exists already. If you find out that you need a new usecase as well, it is up to you if you first implement the new usecase and test it manuelly by invoking the appropriate URIs and then add the menu option or do it vice versa. It is just important that you understand that it will take both: The usecase and the menu option to enable new functionality for the user. </p>
<p>According to the page on the core documentation mentioned above, the CMS menus are defined in an XML document like this: </p>
-<pre>
+<source>
<menu
xmlns="http://apache.org/cocoon/lenya/menubar/1.0"
xmlns:uc="http://apache.org/cocoon/lenya/usecase/1.0"
@@ -71,16 +67,16 @@
</menu>
-</pre>
+</source>
</section><section><title id="head-717f7a242c8db5f6fb81e54e27fcbcf590009452">Edit generic.xsp to add the item for the menu option</title>
<p>In practive this XML is generated of an XSP which you can find in </p>
-<p><tt>lenya/pubs/<your-pub>/config/menus/generic.xsp</tt> </p>
+<p><em>lenya/pubs/<your-pub>/config/menus/generic.xsp</em> </p>
<p>Edit this XSP to add your new menu item! </p>
<p>The XSP is used in the following section of global-sitemap.xmap: </p>
-<pre>
+<source>
<map:match pattern="lenya-page/*/*/**">
<map:generate src="cocoon:/menu-xml/{1}/{2}/{3}"/>
@@ -121,19 +117,19 @@
<map:serialize type="xml"/>
</map:match>
-</pre>
-<p>The <tt><map:generate src="cocoon:/menu-xml/{1}/{2}/{3}"/></tt> is an internal pipeline, which can be found in the same file: </p>
+</source>
+<p>The <em><map:generate src="cocoon:/menu-xml/{1}/{2}/{3}"/></em> is an internal pipeline, which can be found in the same file: </p>
-<pre>
+<source>
<!-- menu-xml/{publication-id}/... -->
<map:match pattern="menu-xml/*/**" internal-only="true">
<map:mount uri-prefix="menu-xml/{1}/" src="lenya/pubs/{1}/menus.xmap" check-reload="true" reload-method="synchron"/>
</map:match>
-</pre>
-<p>This mounts the <tt>lenya/pubs/<your-pub>/menus.xmap</tt> sitemap snippet from the publication which then will decide weather we are in live or authoring mode and generate the menu definition from the publication specific menu.xsp: </p>
+</source>
+<p>This mounts the <em>lenya/pubs/<your-pub>/menus.xmap</em> sitemap snippet from the publication which then will decide weather we are in live or authoring mode and generate the menu definition from the publication specific menu.xsp: </p>
-<pre>
+<source>
<map:match pattern="live/**">
<map:generate type="serverpages" src="../../content/menus/live.xsp"/>
<map:serialize type="xml"/>
@@ -146,21 +142,21 @@
</map:match>
</map:pipeline>
-</pre>
+</source>
</section><section><title id="head-3c7c7b03da78f976501b3a61c43af692d6ced2c4">Double-check usecase and workflow configuration</title>
-<p>If you look back at the <tt>lenya-page/*/*/**</tt> matcher in global-sitemap.xmap above, the menus are built by: </p>
+<p>If you look back at the <em>lenya-page/*/*/**</em> matcher in global-sitemap.xmap above, the menus are built by: </p>
<ul>
<li><p> generating the menu definition from the XSP (which we edited already) </p>
</li>
<li><p> applying the workflowmenu and usecasemenu transformers </p>
</li>
-<li><p> using <tt>lenya/xslt/menu/menu2xhtml.xsl</tt> to generate the XHTML </p>
+<li><p> using <em>lenya/xslt/menu/menu2xhtml.xsl</em> to generate the XHTML </p>
</li>
</ul>
<p>This means if you added your new menu option to the XSP it should show up in the menu. But it might be grayed out. </p>
<p>If this is the case, either the workflowmenu or the usecasemneu transformer decided based on the workflow configuration or based on the usecase policy that this option is not available to this user at this point in time. You may want to check the appropriate configurations to check why this is the case. </p>
-<p>The usecase configuration can be found in <tt>lenya/pubs/<your-pub>/config/ac/usecase-policies.xml</tt> </p></section> </body>
+<p>The usecase configuration can be found in <em>lenya/pubs/<your-pub>/config/ac/usecase-policies.xml</em> </p></section> </body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_screens.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_screens.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_screens.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/cms_screens.xml Sun May 15 16:56:54 2005
@@ -29,9 +29,9 @@
<section><title id="head-707eb025442a6dfa67ca897b5badaf9dee4fb713">File Locations</title>
<ul>
-<li><p> <tt>src/webapp/lenya/xslt/util/page2xhtml.xsl</tt> - The CMS screen stylesheet. </p>
+<li><p> <em>src/webapp/lenya/xslt/util/page2xhtml.xsl</em> - The CMS screen stylesheet. </p>
</li>
-<li><p> <tt>src/webapp/lenya/resources/css</tt> - The CMS screen CSS files. </p>
+<li><p> <em>src/webapp/lenya/resources/css</em> - The CMS screen CSS files. </p>
</li>
</ul>
@@ -39,7 +39,7 @@
<p>Usually a resource is used to style a CMS screen: </p>
-<pre>
+<source>
<map:resource name="style-cms-page">
<map:transform src="lenya/xslt/util/page2xhtml.xsl">
<map:parameter name="contextprefix"
@@ -48,10 +48,10 @@
<map:serialize/>
</map:resource>
-</pre>
+</source>
<p>¨ This resource is called from the pipeline (the example serves the Lenya CMS starting page): </p>
-<pre>
+<source>
<map:match pattern="index.html">
<map:aggregate element="lenya" ...>
<map:part src="cocoon:/publications.xml"/>
@@ -61,13 +61,13 @@
<map:transform src="lenya/xslt/util/welcome.xsl"/>
<map:call resource="style-cms-page"/>
</map:match>
-</pre>
+</source>
</section><section><title id="head-bc001dc9bb21e41435e11b6e1d8d83137c94f57c">Writing a CMS screen</title>
<p>To write a CMS screen, use the following syntax: </p>
-<pre>
+<source>
<page:page xmlns:page="http://apache.org/cocoon/lenya/cms-page/1.0">
<page:title>
@@ -79,12 +79,12 @@
</page:body>
</page:page>
-</pre>
+</source>
</section><section><title id="head-1b28e37b4edb357dcda08a8c350c39abee643a31">Cascading Stylesheets</title>
-<p>When using CSS classes or IDs, please follow the rule that every class or ID starts with the prefix <tt>lenya-</tt>. </p>
-<p>Put your specific CSS file in the CSS directory (see above) and include it in <tt>default.css</tt>. </p>
+<p>When using CSS classes or IDs, please follow the rule that every class or ID starts with the prefix <em>lenya-</em>. </p>
+<p>Put your specific CSS file in the CSS directory (see above) and include it in <em>default.css</em>. </p>
<p>Currently, the following Lenya CSS classes are defined: </p>
<ul>
<li><p> Boxes </p><ul>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/custom_resourcetype.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/custom_resourcetype.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/custom_resourcetype.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/custom_resourcetype.xml Sun May 15 16:56:54 2005
@@ -63,9 +63,9 @@
</section><section><title id="head-d05f4f01dd36c53247e296e75bc2f09a5d801429">Define the resource type ID</title>
-<p>Define the resource type ID in <tt>mypub/config/doctypes/doctypes.xconf</tt> Note that resource types were historically called doctypes, thus the names of the config files. </p>
+<p>Define the resource type ID in <em>mypub/config/doctypes/doctypes.xconf</em> Note that resource types were historically called doctypes, thus the names of the config files. </p>
-<pre>
+<source>
<doctypes>
<!-- Here is the document ID -->
<doc type="myresourcetype">
@@ -93,14 +93,14 @@
<workflow src="workflow.xml"/>
</doc>
-</doctypes></pre>
+</doctypes></source>
</section><section><title id="head-cea12489d4b764632fd61dd792a9e5f90626e11e">Create the schema</title>
-<p>Create relax NG schema: <tt>mypub/config/doctypes/schemas/myresourcetype.rng</tt> </p>
+<p>Create relax NG schema: <em>mypub/config/doctypes/schemas/myresourcetype.rng</em> </p>
<p>Note: This is optional, but important if you want to use the form editors. If you get your XML files that you try to render as a custom resource type from
somewhere else you can omit this step. You can also omit it if you want to create a sample document manually first to see all the rest working and come back to this point later. </p>
-<pre>
+<source>
<?xml version="1.0" encoding="UTF-8"?>
<!--+
| myresourcetype resource type
@@ -151,15 +151,15 @@
</define>
-</grammar></pre>
+</grammar></source>
<p>Note that you can generate Relax NG schemas from sample files by using <a href="http://www.thaiopensource.com/relaxng/trang.html">
Trang</a> or <a href="http://wwws.sun.com/software/xml/developers/relaxngconverter/"> Sun RELAX NG Converter</a> </p>
</section><section><title id="head-ff4bce85b820a235e0f917955b004b766b9a6d41">Resource type matcher</title>
-<p>Add a sourcetype matcher in <tt>mypub/parameter-doctype.xmap</tt>
+<p>Add a sourcetype matcher in <em>mypub/parameter-doctype.xmap</em>
</p>
-<pre>
+<source>
<!-- This file is map:mounted from mypub/publication-sitemap.xmap -->
<map:action name="sourcetype" src="org.apache.cocoon.acting.sourcetype.SourceTypeAction">
@@ -170,7 +170,7 @@
</sourcetype>
</map:action>
-</pre>
+</source>
<p>The parameter-doctype.xmap allows Lenya to determine the resource type of any URI. the mapping provided in here allows to mix and match resource types freely.
It makes use of the <a href="http://forrest.apache.org/docs/cap.html"> Source Type action</a>. There are several ways to identify a resource type,
such as by its root tag, the namespace of its root element or its schema. Please note that the name of the resource type you specify here is used throughout
@@ -185,10 +185,10 @@
</section><section><title id="head-efab8428b801182274861ad033341c99f13bb014">Sample File</title>
-<p>Add a sample file: <tt>mypub/config/doctypes/samples/myresourcetype.xml</tt> </p>
+<p>Add a sample file: <em>mypub/config/doctypes/samples/myresourcetype.xml</em> </p>
<p>The sample file will be used as a template. If you create a new document with this resource type a copy of the sample file will be placed as a starting point.
Therefore it makes sense to set some good defaults here. </p>
-<pre>
+<source>
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
@@ -226,34 +226,34 @@
<h1>New resource type sample</h1>
<p>This sample page is the basis for pages based on this resource type</p>
</body>
-</html></pre>
+</html></source>
</section><section><title id="head-e41c27c12a329ba8438e3a4b228ac2f4e0e3ccd5">Presentation</title>
<ul>
-<li><p> Create presentation XSLT and CSS. If the XSLT and CSS are specific to the publication, you may want to store them in <tt>mypub/xslt/myresourcetype2xhtml.xsl</tt>
- and <tt>mypub/resources/shared/css/myresourcetype.css</tt>, respectively. Take care of the naming conventions for the XSLT files. </p>
+<li><p> Create presentation XSLT and CSS. If the XSLT and CSS are specific to the publication, you may want to store them in <em>mypub/xslt/myresourcetype2xhtml.xsl</em>
+ and <em>mypub/resources/shared/css/myresourcetype.css</em>, respectively. Take care of the naming conventions for the XSLT files. </p>
</li>
-<li class="gap"><p> Copy <tt>mypub/xslt/page2xhtml-xhtml.xsl</tt> to <tt>mypub/xslt/page2xhtml-myresourcetype.xsl</tt>. This will style your new document type
- like your old documents. If you wish to change how the new documents look, create your own stylesheet at <tt>mypub/xslt/page2xhtml-myresourcetype.xsl</tt> </p>
+<li class="gap"><p> Copy <em>mypub/xslt/page2xhtml-xhtml.xsl</em> to <em>mypub/xslt/page2xhtml-myresourcetype.xsl</em>. This will style your new document type
+ like your old documents. If you wish to change how the new documents look, create your own stylesheet at <em>mypub/xslt/page2xhtml-myresourcetype.xsl</em> </p>
</li>
<li class="gap"><p> If you wish to edit your new documents using BXE (Kupu works only with XHTML), you should place a CSS file for styling your documents in
- <tt>mypub/resources/misc/myresourcetype-bxeng.css</tt> </p>
+ <em>mypub/resources/misc/myresourcetype-bxeng.css</em> </p>
</li>
-<li class="gap"><p> Add presentation pipelines in <tt>mypub/sitemap.xmap</tt> if you need special pipelines for your resource type </p>
+<li class="gap"><p> Add presentation pipelines in <em>mypub/sitemap.xmap</em> if you need special pipelines for your resource type </p>
</li>
</ul>
<p>Make sure you understand that for your new resource type you don't need a replacement for page2xhtml.xsl but for xhtml2xhtml. The reason is this: </p>
<p>Transforming a document to a page in the browser is always a two-step process, </p>
-<ol type="1">
+<ol>
<li><p>Using {resourcetype}2xhtml.xsl the document (which might be any arbritary XML such as the link list, Docbook, a RSS feed, etc.) is turned into an XHTML presentation. </p>
</li>
<li><p>This XHTML is then processed to contain nagivation, menus and the like using page2xhtml. </p>
</li>
<li><p>The stylesheet {resourcetype}2xhtml.xsl must return a document of the form
-<tt><div id="body" xmlns="http://www.w3.org/1999/xhtml"> ... </div></tt>. </p>
+<em><div id="body" xmlns="http://www.w3.org/1999/xhtml"> ... </div></em>. </p>
</li>
</ol>
@@ -272,28 +272,28 @@
</ul>
<p>the concept would be </p>
-<pre>
+<source>
document -> rss2xhtml.xsl --+
document -> linklist2xhtml.xsl --+
document -> gallery2xhtml.xsl --+---> page2xhtml.xsl -> Browser
document -> docbook2xhtml.xsl --+
document -> xhtml2xhtml.xsl --+
-</pre>
+</source>
</section><section><title id="head-cb2652bbd893f7f0e164215f740a06953ffb30a1">Menus</title>
<p>Configure the menus (either 1. or 2.) </p>
-<h4 id="head-a546c21eb7f721406e7b0fb338f2241933bb5397">Using an existing menu</h4>
+</section><section><title id="head-a546c21eb7f721406e7b0fb338f2241933bb5397">Using an existing menu</title>
<p>Use an existing menu and add necessary menu items </p>
<ul>
-<li><p> Edit <tt>mypub/config/menus/generic.xsp</tt> and add an entry for the new resource type </p>
+<li><p> Edit <em>mypub/config/menus/generic.xsp</em> and add an entry for the new resource type </p>
</li>
<li><p> </p>
-<pre>
+<source>
...
<menus>
<menu i18n:attr="name" name="File" label="File">
@@ -312,18 +312,18 @@
</xsp:logic>
</block>
-...</pre>
+...</source>
</li>
</ul>
-<h4 id="head-46fd0096d6ae1a5ed8d88f18cc135cf069164b2f">using a custom menu</h4>
+</section><section><title id="head-46fd0096d6ae1a5ed8d88f18cc135cf069164b2f">using a custom menu</title>
<p>or Create a custom menu for this resource type </p>
<ul>
-<li><p> edit <tt>mypub/menus.xmap</tt> </p>
+<li><p> edit <em>mypub/menus.xmap</em> </p>
</li>
-<li><p> create a menu file <tt>mypub/config/menus/myresourcetype.xsp</tt> </p>
+<li><p> create a menu file <em>mypub/config/menus/myresourcetype.xsp</em> </p>
</li>
</ul>
@@ -331,10 +331,10 @@
<p>(optional) define a specific workflow </p>
<ul>
-<li><p> add the workflow schema to <tt>mypub/config/workflow/</tt> </p>
+<li><p> add the workflow schema to <em>mypub/config/workflow/</em> </p>
</li>
-<li><p> assign the workflow schema to the resource type in <tt>mypub/config/doctypes/doctypes.xconf</tt> </p>
+<li><p> assign the workflow schema to the resource type in <em>mypub/config/doctypes/doctypes.xconf</em> </p>
</li>
</ul></section> </body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/deploy_publication.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/deploy_publication.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/deploy_publication.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/deploy_publication.xml Sun May 15 16:56:54 2005
@@ -26,17 +26,17 @@
<body>
<p>How to deploy a publication in Apache Lenya: </p>
-<h4 id="head-4e8484518e11290b9ee62111d0dbd603f11932df">Note:</h4>
+<section><title id="head-4e8484518e11290b9ee62111d0dbd603f11932df">Note:</title>
-<p>It is <strong>not</strong> sufficient to copy the publication directories to the <tt>lenya/pubs</tt> directory of your Lenya installation. This way, the core configuration files are not patched, the libraries are not deployed, and other important deployment steps are not applied. </p>
+<p>It is <strong>not</strong> sufficient to copy the publication directories to the <em>lenya/pubs</em> directory of your Lenya installation. This way, the core configuration files are not patched, the libraries are not deployed, and other important deployment steps are not applied. </p>
-<h4 id="head-25336e7dc2bcad9b79daba07afd7af57b3236a6c">Deploying a Publication</h4>
+</section><section><title id="head-25336e7dc2bcad9b79daba07afd7af57b3236a6c">Deploying a Publication</title>
-<ol type="1">
+<ol>
<li><p>Download the publication to a directory of your choice. For instance: </p>
<ul>
-<li style="list-style-type:none">
+<li>
<source>
/src
/lenya-1.2.x <- $LENYA_HOME
@@ -46,37 +46,37 @@
</li>
</ul>
</li>
-<li><p>Declare the publications in <tt>$LENYA_HOME/local.build.properties</tt> using <tt>pubs.root.dirs</tt> </p>
+<li><p>Declare the publications in <em>$LENYA_HOME/local.build.properties</em> using <em>pubs.root.dirs</em> </p>
<ul>
<li><p> For deploying a single publication, add the publication home directory:
- <tt>pubs.root.dirs=src/webapp/lenya/pubs:../../projects/lenya/pubs/my-pub</tt> </p>
+ <em>pubs.root.dirs=src/webapp/lenya/pubs:../../projects/lenya/pubs/my-pub</em> </p>
</li>
<li><p> For deploying a directory containing publications, add the directory:
- <tt>pubs.root.dirs=src/webapp/lenya/pubs:../../projects/lenya/pubs</tt> </p>
+ <em>pubs.root.dirs=src/webapp/lenya/pubs:../../projects/lenya/pubs</em> </p>
</li>
</ul>
</li>
<li><p>Deploy the publication: </p>
<ul>
-<li><p> Jetty: <tt>$LENYA_HOME> build</tt> </p>
+<li><p> Jetty: <em>$LENYA_HOME> build</em> </p>
</li>
<li><p> Tomcat: </p>
-<ol type="a">
-<li><p><tt>$LENYA_HOME> build install-pub</tt> </p>
+<ol>
+<li><p><em>$LENYA_HOME> build install-pub</em> </p>
</li>
-<li><p>in case if this fails try it in a different way: <tt>$LENYA_HOME> ./build.sh install-pub -Dpub.prefix=""</tt> </p>
+<li><p>in case if this fails try it in a different way: <em>$LENYA_HOME> ./build.sh install-pub -Dpub.prefix=""</em> </p>
</li>
</ol>
</li>
</ul>
</li>
-<li class="gap"><p>Restart the servlet engine </p>
+<li><p>Restart the servlet engine </p>
</li>
<li><p>Go to your Lenya homepage and enjoy the new publication </p>
</li>
-</ol></body>
+</ol></section></body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/external_data.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/external_data.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/external_data.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/external_data.xml Sun May 15 16:56:54 2005
@@ -81,6 +81,6 @@
</map:match></source>
<p>Notice I added the filename requested (without an extension) to the querystring of the remote request.</p>
- <p>2.c Use these filenames for your transformation: <tt>xslt/people2xhtml.xsl</tt> (Use whatever is specified in 2.b, but this is the standard naming convention.)
- <tt>xslt/page2xhtml-people.xsl</tt> I recommend the second option. It is much less code (less chance of bugs), and takes advantage of Lenya's standards.</p></section> </body>
+ <p>2.c Use these filenames for your transformation: <em>xslt/people2xhtml.xsl</em> (Use whatever is specified in 2.b, but this is the standard naming convention.)
+ <em>xslt/page2xhtml-people.xsl</em> I recommend the second option. It is much less code (less chance of bugs), and takes advantage of Lenya's standards.</p></section> </body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/faq.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/faq.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/faq.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/faq.xml Sun May 15 16:56:54 2005
@@ -161,14 +161,10 @@
</ol>
</li>
</ol>
- <br />
- <br />
-
- <hr />
- <h3 id="head-5db5277b98942661b1969971b6efc9174422a105">Errors</h3>
- <h4 id="head-0373b4b0a56b6bc690e427f6fb5f2735d7069b27">I get an error or an
- exception, where can I look at, what should I do?</h4>
- <ol type="1">
+<section><title id="head-5db5277b98942661b1969971b6efc9174422a105">Errors</title>
+ </section><section><title id="head-0373b4b0a56b6bc690e427f6fb5f2735d7069b27">I get an error or an
+ exception, where can I look at, what should I do?</title>
+ <ol>
<li>
<p>Read this FAQ carefully</p>
</li>
@@ -207,21 +203,21 @@
</ul>
</li>
</ol>
- <hr />
- <h3 id="head-abfa1b062bbdbc047382217da6831202617d497d">General Lenya
- capabilities</h3>
- <h4 id="head-87f6d9cc7f4ad578df61301614a51bb0e897d1fb">Can a local Lenya instance
- generate a site that is deployed on a remote hosting service?</h4>
+
+ </section><section><title id="head-abfa1b062bbdbc047382217da6831202617d497d">General Lenya
+ capabilities</title>
+ </section><section><title id="head-87f6d9cc7f4ad578df61301614a51bb0e897d1fb">Can a local Lenya instance
+ generate a site that is deployed on a remote hosting service?</title>
<p>Yes. Using the <a
- href="site:tasksexporter">
+ href="site:taskexporter">
StaticHTMLExporter task</a>, Lenya can generate static html, css, and other
supported files. Lenya maintains the directory structure of the generated site,
which can then be uploaded to another site.</p>
<p>To enable the StaticHTMLExporter task, configure the tasks.xconf file located
in /$PUBLICATION_DIRECTORY/$YOUR_PROJECT_NAME/config/tasks/.</p>
<p>Enable the StaticHTMLExporter as a sub-task of the
- <tt><task id="publish"></tt> task,</p>
-<pre>
+ <em><task id="publish"></em> task,</p>
+<source>
<task id="publish">
....
<task id="export" class="org.apache.lenya.cms.publishing.StaticHTMLExporter">
@@ -231,7 +227,7 @@
<parameter name="my-server-port" value="$THE_SERVER_PORT_RUNNING_LENYA"/>
</task>
</task>
-</pre>
+</source>
<p>When publishing files, the static files will be stored in the "export-path"
directory.</p>
<p>As of Lenya 1.2, this task is included in the publish task, but commented out
@@ -239,45 +235,45 @@
<p>And alternative way is to use the <a href="http://cocoon.apache.org/2.1/userdocs/offline/cli.html"> Cocoon
CLI</a> as there may be some issues with the StaticHTMLExporter, or to call WGet
directly outside of lenya.</p>
- <hr />
- <h3 id="head-462496b77b10044784689a329b76fd6a0e29a3d9">Installation, Setup,
- Virtual hosts etc.</h3>
- <h4 id="head-ca2f8178bd31ced88f4843c3af3055da6f48ea58">I have already deployed
- cocoon in my servlet engine. Can I install Lenya in parallel?</h4>
+
+ </section><section><title id="head-462496b77b10044784689a329b76fd6a0e29a3d9">Installation, Setup,
+ Virtual hosts etc.</title>
+ </section><section><title id="head-ca2f8178bd31ced88f4843c3af3055da6f48ea58">I have already deployed
+ cocoon in my servlet engine. Can I install Lenya in parallel?</title>
<p>Yes you can.</p>
- <hr />
- <h4 id="head-779e3973a215ee2b8959fed75524e04b3de26ad8">Can lenya be integrated
- into a virtual hosting environment?</h4>
+
+ </section><section><title id="head-779e3973a215ee2b8959fed75524e04b3de26ad8">Can lenya be integrated
+ into a virtual hosting environment?</title>
<p>Yes, the probably most simple setup would be to use a standard Apache
webserver with mod_proxy and then connect the various "URL prefixes" to the
various other servers. See the <a
href="site:mod_proxy_and_lenya">Mod Proxy tutorial</a> for reference.</p>
- <hr />
- <h4 id="head-10c56d9e26be7fc0448fc93223ba0c98ee735325">Do I need to create a
- Lenya install for each virtual server?</h4>
+
+ </section><section><title id="head-10c56d9e26be7fc0448fc93223ba0c98ee735325">Do I need to create a
+ Lenya install for each virtual server?</title>
<p>No, you can run all publications within one servlet container context, which
are being called by the virtual servers within Apache for instance.<br />
</p>
- <hr />
- <h4 id="head-251a91fa7416b9f0ef45df8a0e94d08eca719769">Is there a way to create
+
+ </section><section><title id="head-251a91fa7416b9f0ef45df8a0e94d08eca719769">Is there a way to create
multiple sites accessible via various methods of access control (based on who
- owns them)?</h4>
+ owns them)?</title>
<p>Yes, with the Lenya access control framework this is no problem.</p>
- <hr />
- <h4 id="head-be840ede2e55659bcd0df23be98ca6027fcd9b21">How do I enable email
- notifications?</h4>
+
+ </section><section><title id="head-be840ede2e55659bcd0df23be98ca6027fcd9b21">How do I enable email
+ notifications?</title>
<p>Set enabled="true" in lenya/config/notification/notification.xconf</p>
<p>Set the property in pubname/config/tasks/targets.xml to your smtp server
<property name="mail.mailhost" value="localhost"/></p>
- <hr />
- <h3 id="head-427120a2ec8ce5593f2867a0d499dc7038e3d2fd">Running Lenya</h3>
- <h4 id="head-b72382ba8f6f242dbf7a7a0fee47eab6cc630b3a">Lenya CMS ui tabs are not
- displayed, whats wrong?</h4>
+
+ </section><section><title id="head-427120a2ec8ce5593f2867a0d499dc7038e3d2fd">Running Lenya</title>
+ </section><section><title id="head-b72382ba8f6f242dbf7a7a0fee47eab6cc630b3a">Lenya CMS ui tabs are not
+ displayed, whats wrong?</title>
<p>As of Lenya 1.2, this is no longer a problem. It used to be a problem with
Xalan.</p>
- <hr />
- <h4 id="head-8600110d3f153b59ee0fd5487a71a88a7122b615">I can't run the lenya.sh
- script in a linux shell.</h4>
+
+ </section><section><title id="head-8600110d3f153b59ee0fd5487a71a88a7122b615">I can't run the lenya.sh
+ script in a linux shell.</title>
<p>The lenya.sh script has DOS line breaks. Fix it like that.</p>
<ul>
<li>
@@ -291,45 +287,45 @@
</li>
</ul>
<p>...and lenya will work like a charm </p>
- <hr />
- <h4 id="head-7bebb8181baceb522ec7176d0c715e5f4a4a3cd8">Why do I get an "illegal
- cookie" warning with all the lenya reference sites using Opera?</h4>
- <p>cocoon issues a cookie containing <tt>/lenya</tt>. If the path to the Lenya
+
+ </section><section><title id="head-7bebb8181baceb522ec7176d0c715e5f4a4a3cd8">Why do I get an "illegal
+ cookie" warning with all the lenya reference sites using Opera?</title>
+ <p>cocoon issues a cookie containing <em>/lenya</em>. If the path to the Lenya
publication does conflict with the cookie-path, Opera will (rightfully)
complain.</p>
- <hr />
- <h4 id="head-4d1f66d4005aa31c18293b90c01f921d7d6378d4">I get a
- {{{java.net.URISyntaxException}}} error:</h4>
-<pre>
+
+ </section><section><title id="head-4d1f66d4005aa31c18293b90c01f921d7d6378d4">I get a
+ {{{java.net.URISyntaxException}}} error:</title>
+<source>
java.net.URISyntaxException: Illegal character in path at index 21:
file:/D:/build/Tomcat 4.1/webapps/lenya/lenya/pubs/blog/config/ac/passwd/
-</pre>
+</source>
<p>The installation path may not contain spaces: <a
href="site:install"> Lenya
Installation Instructions</a></p>
- <hr />
- <h4 id="head-ce80d1aef0ad610871c0d1c1ec2ce21c6f18d43d">How can I create new
- users?</h4>
+
+ </section><section><title id="head-ce80d1aef0ad610871c0d1c1ec2ce21c6f18d43d">How can I create new
+ users?</title>
<p>Log in initially as "alice" with password "levi". Then go to the admin tab and
you'll see a link for users. You can then add new users and delete existing
ones.</p>
- <hr />
- <h4 id="head-5776aeb902ec6b66c8f0c773045e4a49fdd72e57">When using Lenya, a blank
- page occurs.</h4>
+
+ </section><section><title id="head-5776aeb902ec6b66c8f0c773045e4a49fdd72e57">When using Lenya, a blank
+ page occurs.</title>
<p>This could be caused by an exception which is not caught by Lenya. Look into
the log files of your servlet container (Tomcat) or the command line if logging
is not enabled.</p>
- <hr />
- <h4 id="head-9c9338aa4978e7189a98777c0b0cc041a2f88983">I get a "Connection timed
+
+ </section><section><title id="head-9c9338aa4978e7189a98777c0b0cc041a2f88983">I get a "Connection timed
out" errors such as "org.apache.cocoon.ProcessingException: Unable to get
- transformer handler for cocoon://scheduler/default/xxx"</h4>
+ transformer handler for cocoon://scheduler/default/xxx"</title>
<p>Make sure your machine can get a connection to itself under all its hostnames.
Test by pinging all hostnames. Edit your hosts file if necessary.</p>
- <hr />
- <h3 id="head-073bd0a8a39ff624f3505381f4c7c7bb24bf53db">Document Types (short:
- Doctypes)</h3>
- <h4 id="head-aa106303b52e0aa5703d1e505844420580923d54">Where can I find
- lenya-documentation about the exact meaning of:</h4>
+
+ </section><section><title id="head-073bd0a8a39ff624f3505381f4c7c7bb24bf53db">Document Types (short:
+ Doctypes)</title>
+ </section><section><title id="head-aa106303b52e0aa5703d1e505844420580923d54">Where can I find
+ lenya-documentation about the exact meaning of:</title>
<ul>
<li>
<p>page-envelope</p>
@@ -348,11 +344,11 @@
</li>
</ul>
<p>see <a href="site:pageenvelopemodule">Page envelope module</a></p>
- <h4 id="head-3f16c460f9acf75d805b9754dd7fc0f2812a1e9a">How to create a new
- document type?</h4>
+ </section><section><title id="head-3f16c460f9acf75d805b9754dd7fc0f2812a1e9a">How to create a new
+ document type?</title>
<p>See <a href="site:customresourcetype">Adding Custom Resource Type</a>.</p>
- <h4 id="head-8143b677e57e642774dc8db8cdcbc06a63ac9478">How to to use my own Relax
- NG schema for editing documents with Bitflux in Lenya?</h4>
+ </section><section><title id="head-8143b677e57e642774dc8db8cdcbc06a63ac9478">How to to use my own Relax
+ NG schema for editing documents with Bitflux in Lenya?</title>
<ul>
<li>
<p>You have to create a new document type.</p>
@@ -361,42 +357,42 @@
<p>You have to add the appropriate menu item.</p>
</li>
</ul>
- <hr />
- <h3 id="head-eed52c4e444a9486524fa902254fec7aaf28618b">File-upload</h3>
- <h4 id="head-e945c9c01a86f883cac8203ed9b24917645c3c41">How can I Upload XML
- Files?</h4>
+
+ </section><section><title id="head-eed52c4e444a9486524fa902254fec7aaf28618b">File-upload</title>
+ </section><section><title id="head-e945c9c01a86f883cac8203ed9b24917645c3c41">How can I Upload XML
+ Files?</title>
<p>Does Lenya have something along the lines of a form that will allow people to
upload XML files, have them validated, etc, then publish on a live site?</p>
<p>There is the one form editor (a big text area to edit XML in). Another
possibility is to use WebDAV to import XML files.</p>
- <hr />
- <h3 id="head-6e971f9ed538ab42f352a77825305fcd38eb3447">Compliance to
- standards</h3>
- <h4 id="head-6ef6323947fdd859e7c0994c91f95db530043edc">How to port the default
- pub to XHTML?</h4>
+
+ </section><section><title id="head-6e971f9ed538ab42f352a77825305fcd38eb3447">Compliance to
+ standards</title>
+ </section><section><title id="head-6ef6323947fdd859e7c0994c91f95db530043edc">How to port the default
+ pub to XHTML?</title>
<p>The Default publication is validated as HTML Transitional, how to port it to
XHTML?</p>
<p>The final serialization done in pipeline is to HTML (publication-sitemap.xmap
line 154 ATM). You can change it to XHTML there.</p>
- <hr />
- <h3 id="head-d4b0d0502b0debd341654fdfa20528ece35ca597">Revision Control</h3>
- <h4 id="head-d7ae6004b33695f696e45b752994e1b8a0f79382">How do I break a lock on a
- document?</h4>
+
+ </section><section><title id="head-d4b0d0502b0debd341654fdfa20528ece35ca597">Revision Control</title>
+ </section><section><title id="head-d7ae6004b33695f696e45b752994e1b8a0f79382">How do I break a lock on a
+ document?</title>
<p>Also known as: How can manage this error: "Could not check out the file Reason
: The resource has already been checked out by another user"</p>
<p>unfortunately, currently there is no GUI way to break a lock (but have a look
on the Background). you have to go into
content/rcml/content/authoring/yourpage/index_en.xml.rcml and look at the entries
in there</p>
-<pre>
+<source>
<!CheckOut>
<Identity>lenya</Identity>
<Time>1083252253647</Time>
</!CheckOut>
-</pre>
+</source>
<p>if the most recent (the ones on top) are CheckOut and no corresponding CheckIn
you have a lock. you can break the lock by removing the CheckOut line.</p>
- <h5 id="head-4e29c86a0e361916412b4708eb7e60cb22b54ebd">Background:</h5>
+ </section><section><title id="head-4e29c86a0e361916412b4708eb7e60cb22b54ebd">Background:</title>
<p>If you edit a document, it gets checked out. This means you telling lenya that
you want the exclusive right to change the document. Lenya will lock this
document for other users (so it cannot be edit by someone else). After you
@@ -406,13 +402,13 @@
get checked in (browser crash?) the document remains locked. Log in initially as
"alice" with password "levi". Try to open the document (e.g. with the forms
editor) and hit CANCEL. Then it should be checked-in again.</p>
- <hr />
- <h3 id="head-1942e5ee89668002b8540e44807a663ff96d4626">Edit documents</h3>
- <h4 id="head-e2a3d5bd16858aac474b1c76f18229829feeb763">How can I delete a
- document?</h4>
+
+ </section><section><title id="head-1942e5ee89668002b8540e44807a663ff96d4626">Edit documents</title>
+ </section><section><title id="head-e2a3d5bd16858aac474b1c76f18229829feeb763">How can I delete a
+ document?</title>
<p>To remove a document you have two options:<br />
</p>
- <ol type="1">
+ <ol>
<li>
<p>you can either archive it (and restore it later): In the site tab go to
Edit->Archive.</p>
@@ -421,19 +417,19 @@
<p>or you can delete it: In the site tab go to Edit->Delete</p>
</li>
</ol>
- <hr />
- <h3 id="head-18756b23c0c47e9c1df6d0c2e7eb8f1253cd802b">Asset management</h3>
- <h4 id="head-4644e44019d408c3109df15e500307f00cbd656e">Asset upload does not
- work. How do I enable asset uploads?</h4>
+
+ </section><section><title id="head-18756b23c0c47e9c1df6d0c2e7eb8f1253cd802b">Asset management</title>
+ </section><section><title id="head-4644e44019d408c3109df15e500307f00cbd656e">Asset upload does not
+ work. How do I enable asset uploads?</title>
<p>Edit the file lenya/WEB-INF/web.xml, look for "enable-uploads" and change the
param-value to "true". This is also a build option you can set in
local.build.properties.</p>
- <hr />
- <h3 id="head-d4c2fa687aa75c4c5e32f64aa6258850056b52e7">Fallback</h3>
- <h4 id="head-4bba854b1228b7cb9a59ffd1a7d678bf5ee86513">How can I provide a
- different authoring login page for my publication?</h4>
+
+ </section><section><title id="head-d4c2fa687aa75c4c5e32f64aa6258850056b52e7">Fallback</title>
+ </section><section><title id="head-4bba854b1228b7cb9a59ffd1a7d678bf5ee86513">How can I provide a
+ different authoring login page for my publication?</title>
<p>You've to use Fallbacks. In sitemap.xmap put the login xsl under fallback.</p>
-<pre>
+<source>
<map:match type="step" pattern="showscreen">
<map:generate type="serverpages" src="lenya/content/ac/login.xsp"/>
<map:transform src="lenya/{fallback:xslt/ac/login.xsl}">
@@ -441,19 +437,20 @@
</map:transform>
<map:call resource="style-cms-page"/>
</map:match>
-</pre>
+</source>
<p>And now write your alternative login.xsl in the publication filesystem, under
config/ac (webapps/lenya/lenya/pubs/[pubName]/config/ac)</p>
- <h3 id="head-1fd5cb004f70073184d31e97586ffa693be48d1c">Internationalization
- (i18n)</h3>
- <h4 id="head-19baa282c3fa086fa00d3f5eca95f90da748e27d">How do I switch the
- default language for an existing publication?</h4>
- <p>Go to <tt>lenya/pubs/<youpubname>/config/publication.xconf</tt> and move
- the <tt>default="true"</tt> attribute to your default language.</p>
- <h3 id="head-398df26ef29a65f74145baac60b42b84d8c57f7f">Editors</h3>
- <h4 id="head-0a116c111e424548d1691b1ec04d7e15dcfb9ac9">BXE doesn't let me insert
- a <h1> heading?</h4>
- <p>This is a setting in <tt>lenya/lenya/resources/misc/bxeng/contextmenu.xml</tt>
+ </section><section><title id="head-1fd5cb004f70073184d31e97586ffa693be48d1c">Internationalization
+ (i18n)</title>
+ </section><section><title id="head-19baa282c3fa086fa00d3f5eca95f90da748e27d">How do I switch the
+ default language for an existing publication?</title>
+ <p>Go to <em>lenya/pubs/<youpubname>/config/publication.xconf</em> and move
+ the <em>default="true"</em> attribute to your default language.</p>
+ </section><section><title id="head-398df26ef29a65f74145baac60b42b84d8c57f7f">Editors</title>
+ </section><section><title id="head-0a116c111e424548d1691b1ec04d7e15dcfb9ac9">BXE doesn't let me insert
+ a <h1> heading?</title>
+ <p>This is a setting in <em>lenya/lenya/resources/misc/bxeng/contextmenu.xml</em>
- all tags appearing there cannot be inserted by the BXE popup menu.</p>
+ </section>
</body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/ldap_authentication.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/ldap_authentication.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/ldap_authentication.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/ldap_authentication.xml Sun May 15 16:56:54 2005
@@ -29,16 +29,16 @@
<section><title id="head-c6473a347c56f380b016b80abd50c11a339f65ba">Configuring and activating LDAP in Lenya</title>
-<ol type="1">
-<li><p>Go to the directory <tt>lenya/pubs/<your-publication-name>/config/ac</tt> </p>
+<ol>
+<li><p>Go to the directory <em>lenya/pubs/<your-publication-name>/config/ac</em> </p>
</li>
-<li><p>Edit the file <tt>ac.xconf</tt> and uncomment the line regarding "LDAP support" </p>
+<li><p>Edit the file <em>ac.xconf</em> and uncomment the line regarding "LDAP support" </p>
</li>
-<li><p>Go to the subdirectory <tt>passwd</tt> and copy the file <tt>lenya/pubs/<your-publication-name>/config/ac/passwd/ldap.properties.sample</tt> to the file <tt>ldap.properties</tt> in this directory. </p>
+<li><p>Go to the subdirectory <em>passwd</em> and copy the file <em>lenya/pubs/<your-publication-name>/config/ac/passwd/ldap.properties.sample</em> to the file <em>ldap.properties</em> in this directory. </p>
</li>
-<li><p>Edit the file <tt>ldap.properties</tt> with your settings (the sample file contains explanations for the entries) </p>
+<li><p>Edit the file <em>ldap.properties</em> with your settings (the sample file contains explanations for the entries) </p>
</li>
<li><p>Restart your servlet container, so that the changes take effect </p>
</li>
@@ -51,7 +51,7 @@
</section><section><title id="head-7a25fa154659dcf977c814cc7e12b6a94861a91e">Allowing LDAP users to login</title>
<p>Once you have everything configured OK, you can tell Lenya to allow certain LDAP users. It is important to understand that, just because a user exists in LDAP, does not mean she has access to Lenya. The user needs to be explicitly added in Lenya, along with the group memberships. However, the authentication itself (password handling) is then completely handled through LDAP. </p>
-<ol type="1">
+<ol>
<li><p>In the administration GUI, add the "LDAP user" in order to make this user known to Lenya. You can use the same id for Lenya as the existing LDAP id. </p>
</li>
<li><p>Click on the user and add group settings - if user belongs to no groups at all, she will not be able to login </p>
@@ -86,18 +86,17 @@
</li>
</ul>
-<pre>
-
+<source>
keytool -import -keystore .keystore -file <ca_cert_file> -alias <yourdomain.com>
-</pre>
+</source>
</section><section><title id="head-9019cde2979c770be142ebf7a0c6e03dacaf1480">Notes</title>
<ul>
-<li><p> If you modify <tt>ldap.properties</tt>, it may be necessary to restart your servlet container or at least to reload your webapp in order for the changes to take effect. </p>
+<li><p> If you modify <em>ldap.properties</em>, it may be necessary to restart your servlet container or at least to reload your webapp in order for the changes to take effect. </p>
</li>
-<li><p> Lenya expects the users to be in container called <tt>ou=People</tt> that needs to be nested into the container you provide in the <tt>provider-url</tt> parameter in <tt>ldap.properties</tt>. (Example: <tt>provider-url=ldap://your.ldap.server/ou=intern,dc=example,dc=com</tt> will look for users in <tt>ou=People,ou=intern,dc=example,dc=com</tt>) </p>
+<li><p> Lenya expects the users to be in container called <em>ou=People</em> that needs to be nested into the container you provide in the <em>provider-url</em> parameter in <em>ldap.properties</em>. (Example: <em>provider-url=ldap://your.ldap.server/ou=intern,dc=example,dc=com</em> will look for users in <em>ou=People,ou=intern,dc=example,dc=com</em>) </p>
</li>
</ul>
@@ -106,11 +105,11 @@
<p>The "University of Zurich Publication" is an example of a publication which uses LDAP authentication. You may wish to install and configure it to authenticate against your LDAP server: this way, you can check whether LDAP authentication is working, before proceeding to activate it in another application. </p>
<p>Note: this HOW-TO was tested using the "University of Zurich Publication" state on May 26th, 2004. If another version is incompatible with your Lenya installation, don't despair, you will still be able to use the LDAP relevant stuff. </p>
-<ol type="1">
+<ol>
<li><p>Retrieve the University of Zurich Lenya publications (unitemplate, unizh) described on <a href="http://wyona.org/">http://wyona.org/</a> </p>
</li>
-<li><p>Go to the <tt>unitemplate/config/ac/passwd</tt> directory and edit <tt>ldap.properties</tt> as described above </p>
+<li><p>Go to the <em>unitemplate/config/ac/passwd</em> directory and edit <em>ldap.properties</em> as described above </p>
</li>
<li><p>if secure LDAP is required, add the server certificate to the keystore as described above </p>
</li>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/look_and_feel.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/look_and_feel.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/look_and_feel.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/look_and_feel.xml Sun May 15 16:56:54 2005
@@ -25,7 +25,7 @@
</header>
<body>
<p>To change your copy of the Default publication into your publication and have some first successes, you probably want to work on two things: </p>
-<ol type="1">
+<ol>
<li><p>Change the color scheme and fonts to your own taste. </p>
</li>
@@ -57,7 +57,7 @@
<p>Have a look at the file $LENYA_DIR/your_pub_name/xslt/page2xhtml.xsl and look for this piece in it: </p>
-<pre>
+<source>
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td id="publication-title">Welcome to the Default Publication!</td>
@@ -65,7 +65,7 @@
<td id="project-logo"><img src="{$root}/images/project-logo.png"/></td>
</tr>
</table>
-</pre>
+</source>
<p>This is the page header. Put in what you want. It's that simple! </p>
</section><section>
<title id="head-3c25d4848127ea4921c40dfeee910b6a0216b60a">Altering navigational components (Tabs, Breadcrumbs and Menus)</title>
@@ -75,19 +75,19 @@
<p>The navigational elements are built from the file sitetree.xml (look for it in the directory structure) using XSLTs that are usually global to Lenya and therefore not part of you publication. But the global XSLTs can be overridden with local ones quite easily. </p>
<p>All it takes is to create the files </p>
-<pre>
+<source>
$LENYA_DIR/lenya/pubs/__your_pub_name__/lenya/xslt/navigation/breadcrumbs.xsl
$LENYA_DIR/lenya/pubs/__your_pub_name__/lenya/xslt/navigation/tabs.xsl
$LENYA_DIR/lenya/pubs/__your_pub_name__/lenya/xslt/navigation/menu.xsl
-</pre>
+</source>
<p>which will be used in favor of the core files </p>
-<pre>
+<source>
$LENYA_DIR/lenya/lenya/xslt/navigation/breadcrumbs.xsl
$LENYA_DIR/lenya/lenya/xslt/navigation/tabs.xsl
$LENYA_DIR/lenya/lenya/xslt/navigation/menu.xsl
-</pre>
-<p>Usually, you will not want to use a completely different version of the stylesheet. So it is recommended to include the core file using <tt><xsl:import/></tt>. </p>
+</source>
+<p>Usually, you will not want to use a completely different version of the stylesheet. So it is recommended to include the core file using <em><xsl:import/></em>. </p>
<p>This is possible because of a built-in fallback mechanism that will make Lenya use the global XSLTs in case there are no local versions inside the publication.
See the <a href="site:navigation">Navigation Framework</a> for details on this. </p> </section></body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_mime_type.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_mime_type.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_mime_type.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_mime_type.xml Sun May 15 16:56:54 2005
@@ -30,22 +30,22 @@
<section><title id="head-a4bbfe45a08bfc3cc5d0cd1bcfff7fa83460fca6">Enabling the downloads</title>
-<p>The resource types which are known to your Lenya installation are defined in the file <tt>lenya/resources.xmap</tt>. Add the new Mime-Type in here, for example for AVI this is:
+<p>The resource types which are known to your Lenya installation are defined in the file <em>lenya/resources.xmap</em>. Add the new Mime-Type in here, for example for AVI this is:
</p>
-<pre>
+<source>
<map:match pattern="*/*/**.avi">
<map:read src="pubs/{1}/resources/{2}/{3}.avi" mime-tyoe="video/x-msvideo" />
</map:match>
-</pre>
+</source>
<p>You probably need to restart your servlet container in order for the changes to take effect. </p>
<p>Now, visitors of your pages should be able to download objects of this mime-type. </p>
</section>
<section><title id="head-c0a473eaffabfbcc5c34cdb6c5efff7ab9e5b7f4">Enabling uploading for content editors</title>
<p>In the asset handling, there are some restrictions as to what filetypes you are allowed to upload. If the file extension you require is not yet allowed,
-edit the file <tt>xslt/authoring/asset.xsl</tt> and add it to the list of types defined in <tt> <xsl:param name="extensions" ...</tt> </p>
+edit the file <em>xslt/authoring/asset.xsl</em> and add it to the list of types defined in <em> <xsl:param name="extensions" ...</em> </p>
-<p>If you are using BXE, edit the file <tt>xslt/bxeng/asset.xsl</tt> and add it to the list of types defined in <tt><xsl:param name="extensions" ...</tt> </p>
+<p>If you are using BXE, edit the file <em>xslt/bxeng/asset.xsl</em> and add it to the list of types defined in <em><xsl:param name="extensions" ...</em> </p>
</section></body>
</document>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_publication.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_publication.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_publication.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/new_publication.xml Sun May 15 16:56:54 2005
@@ -29,7 +29,7 @@
Although this situation will change for 1.4 (it already has a 'New Publication' wizard), at the moment threse are the steps that you should follow. </p>
<p><strong>Note:</strong> At the moment, you need the source distribution of Lenya to create new publications.
- <strong>Note:</strong> All <tt>http://localhost</tt> URLs on this page are assuming that you use the Jetty servlet engine. </p>
+ <strong>Note:</strong> All <em>http://localhost</em> URLs on this page are assuming that you use the Jetty servlet engine. </p>
<p>Attached is a diagram of a <a href="typical-lenya-setup.pdf">typical Lenya setup</a>. </p>
<p>First of all make a copy of the default publication and rename it (the new publication is named NEW-PUB). </p>
@@ -53,28 +53,28 @@
</source>
<p>Then follow these steps: </p>
-<ol type="1">
-<li><p>Move to <tt>$NEW_PUB_HOME</tt> folder and edit the <tt>publication.xml</tt> file in this directory to describe your new publication. Specifically, edit the <tt>/lenya:publication/lenya:name</tt> tag to reflect the name of your publication. </p>
+<ol>
+<li><p>Move to <em>$NEW_PUB_HOME</em> folder and edit the <em>publication.xml</em> file in this directory to describe your new publication. Specifically, edit the <em>/lenya:publication/lenya:name</em> tag to reflect the name of your publication. </p>
</li>
-<li><p>Move to <tt>$NEW_PUB_HOME/config/ac/</tt> and edit <tt>ac.xconf</tt> changing every occurence of default to NEW-PUB; </p>
+<li><p>Move to <em>$NEW_PUB_HOME/config/ac/</em> and edit <em>ac.xconf</em> changing every occurence of default to NEW-PUB; </p>
</li>
-<li><p>Move to <tt>$NEW_PUB_HOME/config/tasks/</tt> and edit <tt>targets.xml</tt> changing <tt><property name="export.expression" value="/lenya/default/live/"/></tt> to <tt><property name="export.expression" value="/lenya/NEW-PUB/live/"/></tt>. </p>
+<li><p>Move to <em>$NEW_PUB_HOME/config/tasks/</em> and edit <em>targets.xml</em> changing <em><property name="export.expression" value="/lenya/default/live/"/></em> to <em><property name="export.expression" value="/lenya/NEW-PUB/live/"/></em>. </p>
</li>
<li><p>Deploy your publication (see <a href="site:deploypub">Deploy Publication How-To</a>) </p>
</li>
-<li><p>The should then show up on the page at <tt>http://localhost:8888</tt>; </p>
+<li><p>The should then show up on the page at <em>http://localhost:8888</em>; </p>
</li>
-<li><p>Add new users using <tt>http://localhost:8888/NEW-PUB/admin/users.html</tt> (for security reasons it's better to remove default users or at least change passwords) If you get a Java Script error,
+<li><p>Add new users using <em>http://localhost:8888/NEW-PUB/admin/users.html</em> (for security reasons it's better to remove default users or at least change passwords) If you get a Java Script error,
check if the files under NEW-PUB have the correct permissions to be modified by your servlet engine; </p>
</li>
<li><p>Delete pages of default publication leaving only the Home page available. Probably you would like to delete german pages (german is labelled with "de" string) and add your language: </p>
-<ol type="1">
-<li><p>in Authoring mode <tt>http:/localhost:8888/NEW-PUB/info-authoring/index.html?lenya.usecase=info-overview&lenya.step=showscreen</tt>, click on "de" tab and start removing the german pages </p>
+<ol>
+<li><p>in Authoring mode <em>http:/localhost:8888/NEW-PUB/info-authoring/index.html?lenya.usecase=info-overview&lenya.step=showscreen</em>, click on "de" tab and start removing the german pages </p>
</li>
-<li><p>edit the <tt>$NEW_PUB_HOME/config/publication.xconf</tt> file removing the element <tt><language>de</language></tt>
+<li><p>edit the <em>$NEW_PUB_HOME/config/publication.xconf</em> file removing the element <em><language>de</language></em>
(be sure you have removed all german pages before) and eventually add you language. Pay attention, you can add your language even if there's no available translation for the Lenya CMS
interface (i.e. you can add "ru" for russian even if available Lenya is translated only in english or german). The servlet container has to be restarted to apply the changes to the language configuration. </p>
@@ -83,10 +83,10 @@
</li>
</ol>
<p>Optional: </p>
-<ol type="1">
-<li><p>Move to <tt>$NEW_PUB_HOME/config/doctypes/samples/</tt> and edit <tt>xhtml.xml</tt> changing the page that is shown when you create a new document. </p>
+<ol>
+<li><p>Move to <em>$NEW_PUB_HOME/config/doctypes/samples/</em> and edit <em>xhtml.xml</em> changing the page that is shown when you create a new document. </p>
</li>
-<li><p>Start changing the look & feel of default publication to the one you want to your new publication. See: <a href="/lenya/ApplicationLookandFeelHowto">ApplicationLookandFeelHowto</a> </p>
+<li><p>Start changing the look & feel of default publication to the one you want to your new publication. See: <a href="site:lookandfeel">Look & Feel How-To</a> </p>
</li>
<li><p>Deploy your publication when you made changes to the source. </p>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/search.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/search.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/search.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/search.xml Sun May 15 16:56:54 2005
@@ -48,9 +48,9 @@
<p>NOTE: Replace {pub} with your publication name in all instructions.</p>
</section>
<section><title>Indexing on Windows</title>
- <p>This assumes Lenya 1.2.2 was installed to C:\apache-lenya-1.2.2 If your installation is different, adjust the paths. The indexer adds namespaces to the data of Fields in the index. The namespaces are not used (and are annoying), so remove them. An alternative is to fix the XML later, but why bother? File: <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\WEB-INF\classes\org\apache\lenya\lucene\index\configuration2xslt.xsl</tt> Add the following line:</p>
+ <p>This assumes Lenya 1.2.2 was installed to C:\apache-lenya-1.2.2 If your installation is different, adjust the paths. The indexer adds namespaces to the data of Fields in the index. The namespaces are not used (and are annoying), so remove them. An alternative is to fix the XML later, but why bother? File: <em>C:\apache-lenya-1.2.2\build\lenya\webapp\WEB-INF\classes\org\apache\lenya\lucene\index\configuration2xslt.xsl</em> Add the following line:</p>
<source><xsl:template match="namespace"/></source>
- <ol><li>Set the configuration by changing: <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\config\search\lucene-live.xconf</tt>
+ <ol><li>Set the configuration by changing: <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\config\search\lucene-live.xconf</em>
To:
<source>
<?xml version="1.0"?>
@@ -63,7 +63,7 @@
<extensions src="xml"/>
</indexer>
</lucene></source></li>
- <li> Create a new file in the same directory to tell lucene what fields to index (filename must match the configuration src in lucene-live.xconf): <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\config\search\lenyadocs.xconf</tt>
+ <li> Create a new file in the same directory to tell lucene what fields to index (filename must match the configuration src in lucene-live.xconf): <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\config\search\lenyadocs.xconf</em>
Add this:
<source><?xml version="1.0"?>
<luc:document xmlns:luc="http://apache.org/cocoon/lenya/lucene/1.0">
@@ -93,7 +93,7 @@
<luc:field name="contents" type="UnStored" xpath="/"/>
</luc:document></source>
</li>
- <li> Create a batch file: <tt>C:\apache-lenya-1.2.2\tools\bin\Index-{pub}.bat</tt> With this:
+ <li> Create a batch file: <em>C:\apache-lenya-1.2.2\tools\bin\Index-{pub}.bat</em> With this:
<source>
SET LENYAPUB={pub}
SET CLASSPATH=.
@@ -103,7 +103,7 @@
index</source>
</li>
- <li> To create a logfile (and avoid some ant errors), create a file: <tt>C:\apache-lenya-1.2.2\tools\bin\log4j.properties</tt> With this:
+ <li> To create a logfile (and avoid some ant errors), create a file: <em>C:\apache-lenya-1.2.2\tools\bin\log4j.properties</em> With this:
<source>
log4j.rootLogger=INFO, lucene
log4j.appender.lucene = org.apache.log4j.FileAppender
@@ -121,8 +121,8 @@
<li>These are fixed in the next section.</li></ol>
</section><section><title>Fix the XML results to be usable.</title>
- <p>Copy <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\xslt\search\sort.xsl</tt> To: <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\search\sort.xsl</tt>. Copy <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\xslt\navigation\search.xsl</tt>
- to <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\navigation\search.xsl</tt>
+ <p>Copy <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\xslt\search\sort.xsl</em> To: <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\search\sort.xsl</em>. Copy <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\xslt\navigation\search.xsl</em>
+ to <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\navigation\search.xsl</em>
After the other params, add this line:</p>
<source><xsl:param name="chosenlanguage"/></source>
<p>Add the usecase and language fields to the form tag:</p>
@@ -133,7 +133,7 @@
<input class="searchfield" type="text" name="query" alt="Search field"/>
<input class="searchsubmit" type="submit" value="Search" name="find"/>
</form></source>
- <p><a href="search-and-results.xsp">Download</a> new file: <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\content\search\search-and-results.xsp</tt> Based on <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\content\search\search-and-results.xsp</tt></p>
+ <p><a href="search-and-results.xsp">Download</a> new file: <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\content\search\search-and-results.xsp</em> Based on <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\content\search\search-and-results.xsp</em></p>
<ul>
<li>Removed useless information. (I like dynamic lists better than anyone, but Search is a standard function with standard outputs, so why bother? I only left the <fields> tag to separate our output from lucene's.)</li>
<li>Added language filter.</li>
@@ -143,7 +143,7 @@
<li>Fixed counters and total. (Total-hits changed from property to element of results.)</li>
<li>Other bug fixes</li></ul>
- <p><a href="searchfixer.xsl">Download</a> new file: <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\search\searchfixer.xsl</tt> This file converts our poor output to something usable.</p>
+ <p><a href="searchfixer.xsl">Download</a> new file: <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\lenya\xslt\search\searchfixer.xsl</em> This file converts our poor output to something usable.</p>
<ul><li>Add languages to configuration</li>
<li>Move total-hits from element to property of results.</li>
<li>Choose "title" from "htmltitle" or Lucene's "title".</li>
@@ -152,12 +152,12 @@
<li>The default is to use htmlbody for the excerpt. <strong>This file must be modified when using Custom Doctypes that do not have a /html/body.</strong></li>
</ul>
<p><a href="usecase-search.xmap">Download</a> new file:
- <tt>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\usecase-search.xmap</tt></p>
+ <em>C:\apache-lenya-1.2.2\build\lenya\webapp\lenya\pubs\{pub}\usecase-search.xmap</em></p>
</section><section><title>Blocking default search.</title>
<p> It is important to block the default search when implementing ProtectedAreas to prevent visitors from typing the URL of the default search (or, if this publication was in production, using a bookmark to the old search) and seeing links to protected documents.</p>
<ul>
- <li> Create new file: <tt>build\lenya\webapp\lenya\pubs\{pub}\lenya\lucene.xmap</tt></li>
+ <li> Create new file: <em>build\lenya\webapp\lenya\pubs\{pub}\lenya\lucene.xmap</em></li>
<li>Add content:
<source>
<?xml version="1.0" encoding="UTF-8"?>
Modified: lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/site_navigation.xml
URL: http://svn.apache.org/viewcvs/lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/site_navigation.xml?rev=170282&r1=170281&r2=170282&view=diff
==============================================================================
--- lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/site_navigation.xml (original)
+++ lenya/docu/src/documentation/content/xdocs/1_2_x/how-to/site_navigation.xml Sun May 15 16:56:54 2005
@@ -28,12 +28,12 @@
<section><title id="head-da34b3ca6421ef687314b2fc0830c891b3cfa8d7">Technical Background: How Lenya builds the site navigation</title>
-<p>The source of all navigation elements is the sitetree, which you can find in <tt>PUB_HOME/authoring/sitetree.xml</tt>, <tt>PUB_HOME/live/sitetree.xml</tt>, <tt>PUB_HOME/trash/sitetree.xml</tt> or <tt>PUB_HOME/archive/sitetree.xml</tt> depending on the relevant area. </p>
-<p>The tree you can see in the left half of the screen when you access the <tt>Site</tt> tab in authoring mode is pretty much a 1:1 representation of the site tree. </p>
+<p>The source of all navigation elements is the sitetree, which you can find in <em>PUB_HOME/authoring/sitetree.xml</em>, <em>PUB_HOME/live/sitetree.xml</em>, <em>PUB_HOME/trash/sitetree.xml</em> or <em>PUB_HOME/archive/sitetree.xml</em> depending on the relevant area. </p>
+<p>The tree you can see in the left half of the screen when you access the <em>Site</em> tab in authoring mode is pretty much a 1:1 representation of the site tree. </p>
<p>The sitetree.xml document of the default publication which we will use as an example here looks like this: </p>
-<pre>
+<source>
<?xml version="1.0" encoding="UTF-8"?>
<site i18n:attr="label" label="Authoring"
xmlns="http://apache.org/cocoon/lenya/sitetree/1.0"
@@ -83,7 +83,7 @@
</node>
</site>
-</pre>
+</source>
<p>The default publication defines three navigation elements: </p>
<ul>
@@ -137,16 +137,16 @@
<p> </p>
<p>a typical navigation could look this this: </p>
-<pre>
+<source>
+--------------------------------------------------------------------
| | *HOME* | Products | Services |
+--------------------------------------------------------------------
|
-</pre>
+</source>
<p>when the user clicks on Producs, a menu will show up: </p>
-<pre>
+<source>
+--------------------------------------------------------------------
| | Home | *PRODUCTS* | Services |
+--------------------------------------------------------------------
@@ -154,10 +154,10 @@
| - Consumer Products
| - Industrial Products
|
-</pre>
+</source>
<p>clicking on Services will show up a different menu: </p>
-<pre>
+<source>
+--------------------------------------------------------------------
| | Home | Products | *SERVICES* |
@@ -168,34 +168,34 @@
| - 24-hour Emergency
| Hotline
-</pre>
+</source>
-<h5 id="head-5180937f0e533c5948230c73f141c9b2c1aecb65">Simple solution: Hide the menus using CSS</h5>
+</section><section><title id="head-5180937f0e533c5948230c73f141c9b2c1aecb65">Simple solution: Hide the menus using CSS</title>
<p>This behaviour can be achieved by changing the CSS of the default publication. Edit the file </p>
-<pre>
+<source>
$PUB_HOME/resources/shared/css/page.css
-</pre>
-<p>and add the following snippet, preferrably beneath the existing <tt>menublock</tt> declarations: </p>
+</source>
+<p>and add the following snippet, preferrably beneath the existing <em>menublock</em> declarations: </p>
-<pre>
+<source>
.menublock-1 {
display: none;
}
-</pre>
+</source>
<p>This way, all non-selected first level menu entries are hidden, which comprises all menu entries belonging to the other tabs. </p>
-<h5 id="head-f6b2dc82fbfce6cdd76a5552ee76fcdd6fd55d53">Advanced solution: Exclude the menus using XSLT</h5>
+</section><section><title id="head-f6b2dc82fbfce6cdd76a5552ee76fcdd6fd55d53">Advanced solution: Exclude the menus using XSLT</title>
<p>In this approach, you use a custom XSLT stylesheet to generate the menubar XHTML snippet. The file has to be placed at </p>
-<pre>
+<source>
$PUB_HOME/lenya/xslt/navigation/menu.xsl
-</pre>
-<p>Note the step <tt>/lenya</tt> in the path, this is necessary to tell Lenya that you're overriding a file from the core. The stylesheet might look as follows: </p>
+</source>
+<p>Note the step <em>/lenya</em> in the path, this is necessary to tell Lenya that you're overriding a file from the core. The stylesheet might look as follows: </p>
-<pre>
+<source>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
@@ -216,14 +216,14 @@
</xsl:template>
</xsl:stylesheet>
-</pre>
+</source>
<ul>
<li><p> First, you import the core menu XSL so that you can reuse most of the core functionality. </p>
</li>
-<li><p> The first <tt><xsl:template></tt> excludes all top-level <tt><nav:node></tt> entries which don't contain the current item. </p>
+<li><p> The first <em><xsl:template></em> excludes all top-level <em><nav:node></em> entries which don't contain the current item. </p>
</li>
-<li><p> The second <tt><xsl:template></tt> is optional. If you include it, the top-level menu items won't be displayed in the menubar. </p>
+<li><p> The second <em><xsl:template></em> is optional. If you include it, the top-level menu items won't be displayed in the menubar. </p>
</li>
</ul></section></body>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@lenya.apache.org
For additional commands, e-mail: commits-help@lenya.apache.org