Hi Rainer,The time-based activation is entirely handled by the workflow. If you look at the workflow definition, you'll see elements like
<if>
<defined field-value="startDate"/>
<sleep until="${f:startDate}"/>
</if>
... which means you can completely change the behavior if needed.If the wf module is disabled or not installed, well, all of this is completely ignored, so your page 1) gets activated immediately 2) does not get deactivated by magic either.
However, I'm puzzled: what do you mean by "[the page lands directly at publish instance] - but is not shown in frontend" ?
PS. Did something change at timebased activation between 3.5.4 and 3.5.8?
check the changelogs in Jira. Maybe some fixes were applied to the default workflow definition, but it shouldn't have impacted this other than fixing it. Why do you ask ?
-g On Aug 14, 2008, at 12:27 PM, rainer wrote:
2. workflow is disabled - but module is still present ------------------------------------------------i configfure the start- and end-date; activate the page; the page lands directly at publish instance - but is not shown in frontend; first when thestart-date is reached the page is being shown. But doesn't disappear anymore. --> this doesnt work completely How comes the different behaviour? Will the timebased activation work without the workflow module? greetings rainerPS. Did something change at timebased activation between 3.5.4 and 3.5.8?-- View this message in context: http://www.nabble.com/curious-behaviour-of-timebased-activation-tp18979141p18979141.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
