Enable the publishing queue functionality

Asynchronous publishing is switched off as shipped. It is switched on with one setting in content.ini; the other settings of the group tune the queue.

# settings/override/content.ini.append.php
[PublishingSettings]
# enabled | disabled (shipped)
AsynchronousPublishing=enabled
# how many publications the daemon runs at the same time (default 10)
PublishingProcessSlots=10
# seconds between two looks at the queue (default 1)
AsynchronousPollingInterval=1
# seconds between two clean-ups of the queue (default 43200, 12 hours)
AsynchronousCleanupInterval=43200
# age in seconds of finished entries the clean-up removes (default 604800, one week)
AsynchronousCleanupAgeLimit=604800

Clear the INI caches after the change, and start the daemon (Starting the daemon manually, Setting up the service). Without a running daemon, drafts stay in the queue and are not published.

Switching it on per siteaccess

The setting is read where the editor publishes, so it can be set per siteaccess: enable it in settings/siteaccess/<admin siteaccess>/content.ini.append.php for the administration only. With AsynchronousPublishing=disabled nothing is queued and publishing happens in the editor's request, as without the feature.

Publications that are never queued

• A publication without notification (the Publish without notification button) is published at once, because the queue would lose the choice.
• A filter can keep objects out of the queue (see Implementation of a filtering hook).
• Code can switch the queue off for its own publications with the publishing behaviour (ezpContentPublishingBehaviour, disableAsynchronousPublishing), as scripts and imports do.

Cleaning the queue

The queue is the table ezpublishingqueueprocesses. Every AsynchronousCleanupInterval seconds the daemon removes the entries of finished publications older than AsynchronousCleanupAgeLimit.