Niels van Kampenhout wrote:
Hi Francesco,
Francesco Chicchiriccò wrote:
messing around with workflow in Hippo CMS (release 6.05.02), I was
trying to do what is briefly described in [1], and eventually I
even succeeded.
Problems arose when I tried to have two types, one with a
specified workflow, and another with the default one; referring to
the sample in [1], my situation was like this:
<types>
<resources default="practice">
<resource name="practice" label="Practice page">
<schema>repository://types/practice/text.xsd</schema>
<layout>repository://types/practice/layout.xml</style>
<template>repository://types/practice/text.xml</template>
<bl>repository://types/practice/businesslogic.xml</bl>
<i18n>repository://types/practice/i18n</i18n>
</resource>
<resource name="practice-intranet" label="Practice page for
Intranet">
<schema>repository://types/practice/text.xsd</schema>
<layout>repository://types/practice/layout.xml</style>
<template>repository://types/practice/text.xml</template>
<bl>repository://types/practice/businesslogic.xml</bl>
<i18n>repository://types/practice/i18n</i18n>
<workflowName>TaxonomyDocumentIntranet</workflowName>
</resource>
....
</resources>
</types>
Surprisingly, "TaxonomyDocumentIntranet" is chosen for "practice"
as well: I was expecting to have "ReviewedActions" for "practice"
instead, which is the default one.
That's what I'd expect too.
Should it be working like that?
I don't think so. Might be a bug. But the workaround is very simple
of course: just add <workflowName>ReviewedActions</workflowName> to
"practice"...
Of course.... ;-)
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
