This is a 'hot-fix' release to enhance the publishing system:
Improvements to the publishing log output:
The Crisisworks email platform has a maximum message size limit of approximately 5MB; if an email fails to send because this limit has been exceeded, the publishing log now indicates that this is the reason for the failure.
If an email bounces for any reason, the publishing log now indicates that this is the reason for the failure.
If no messages are sent because no recipients match the publishing criteria, the publishing log now indicates this.
When an item is published, the actual sending of messages is done in a background queue process. Previously the item was only reverted to its non-publish state once this process completed. This meant that if the item was updated again during the processing window, another publishing process could inadvertently be triggered. The publishing process has been changed so that now items are reverted to their non-publish state as soon as the publishing process has been triggered. This means that the items can then be updated immediately without the possibility of accidental publishing.