hi thorsten, hi everybody!
i'm trying to add a footer to each page that says "this page was last
edited by <user> on <date>". i've added thorsten's
LenyaMetaDataGenerator into my pipeline, but the workflow field is weird:
<lenya:workflowVersion>
0 event:edit state:authoring user:webmaster machine:127.0.0.1
date:2006-01-24_11:52:02 var:is_live=false
</lenya:workflowVersion>
at the heart of a xml publishing framework, such a data format is a
little, erm, unfortunate, to put it gently.
is there any chance that the data can be re-factored into a clean xml
format?
*.*
i would also like the user name to contain a mailto: link, i.e. i need
to look up the user's email address in the account database. is there
already a method to make this data available to a pipeline?
*.*
thorsten, when i look at the metadata for a document that has been
edited multiple times, the workflowVersion tags are combined into one,
like this:
<lenya:workflowVersion>
0 event:edit state:authoring user:webmaster machine:127.0.0.1
date:2006-01-24_11:52:02 var:is_live=false1 event:submit state:review
user:webmaster machine:127.0.0.1 date:2006-01-24_11:59:17
var:is_live=false2 event:publish state:live user:webmaster
machine:127.0.0.1 date:2006-01-24_11:59:24 var:is_live=true3 event:edit
state:authoring user:webmaster machine:127.0.0.1
date:2006-01-24_14:32:20 var:is_live=true4 event:submit state:review
user:webmaster machine:127.0.0.1 date:2006-01-24_14:32:34
var:is_live=true5 event:publish state:live user:webmaster
machine:127.0.0.1 date:2006-01-24_14:32:40 var:is_live=true6 event:edit
state:authoring user:lenya machine:127.0.0.1 date:2006-02-18_18:50:25
var:is_live=true7 event:submit state:review user:lenya machine:127.0.0.1
date:2006-02-18_18:50:35 var:is_live=true
</lenya:workflowVersion>
bug or feature? if it's a feature, how do i turn it off?
*.*
why does the LenyaMetaDataGenerator example use a different syntax than
the other components in the main aggregator?
<map:part src="cocoon://modules/sitetree/{2}/{3}/menu/{5}.xml"/>
vs.
<map:part src="cocoon:/{2}/{3}/meta?docid={page-envelope:document-id}"/>
can't this for the sake of consistency become
<map:part src="cocoon://modules/metadata/{2}/{3}/meta/{5}.xml"/>
this would imply to move the implementation to a module and have an
extra sitemap, but the analogy to other components makes it easier for
the user imho. what do you think?
regards,
jörn
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
if you are a free (as in "free speech") software developer
and you happen to be travelling near my home, drop me a line
and come round for a free (as in "free beer") beer. :-D
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
