Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Wait until date


Makes it possible to delay the publishing of objects.


This event makes it possible to delay the publishing of certain objects. It can be connected to either the "content/publish/before" trigger or the "content/publish/after" trigger. The following screenshot shows the edit interface for this event.

Edit interface for the "Wait until date" event.

Edit interface for the "Wait until date" event.

Parameters and usage

The "Class" menu makes it possible to select a class that should be affected by the event. When a class is selected, the "Update attributes" button must be used to update the contents of the "Attribute" menu. It will allow the selection of the attribute which is used to enter the date and time when the object should be published. This attribute must be represented by the "Date and time" datatype. Once the correct attribute it selected, the "Select attribute" button must be used to add it to the list below (labeled "Class / attribute combinations"). All objects that are instances of the classes added to this list will be affected by the event. The objects will be published automatically (by the way of the cronjob script) when the given date / time is reached.

If the "Modify the objects' publishing dates" checkbox is checked, the system will update the modification time of the objects when they are published by the system. If unchecked, the date / time when the objects were published by the users will be used.

Balazs Halasy (25/04/2005 1:42 pm)

Balazs Halasy (28/04/2005 2:30 pm)


  • content/publish/after?

    What's the point of using the content/publish/after trigger? Then the object will be published right away, and republished at the given time. For what I would call the expected behaviour, use only content/publish/before.
    • Re: content/publish/after?

      Publish after can be used for you to delay the start of another workflow which is after the waituntildate, because the other workflow wont start until the waituntildate is finished.