Publishing objects asynchronously

With asynchronous publishing enabled and the daemon running, publishing looks like this to an editor:

1. The editor presses Publish in the edit form. The draft is put in the publishing queue, and the page Your content is being published opens (/content/queued/<object ID>/<version>): "Please wait while your content is being published".
2. The page asks for the status of the publication at regular intervals, without reloading, and shows how often it has checked.
3. When the daemon has published the version, the page says Publishing finished, "Your content has been published successfully", with a link to View the published item.

The editor does not have to wait on this page: the publication goes on in the background, and the object shows the new version once it is published.

The states of a queued publication

A draft of an object whose earlier version is still being published waits until that one is done. If something goes wrong the page shows an error, and var/log/async.log has the details.

The page needs the policy content/edit. Without a running daemon, publications stay Pending: check the daemon first when editors report that content is "stuck being published".