[invalid] Problem on update article? email not sent ?

jrodgar wrote: First, it would be more coherent if the approval is always asked on the same way, from a usability point of view

hhmm first time is new content, then it is updating content, anyway in both cases (new / existing) the user receives a message of what is happening

jrodgar wrote: Second, and maybe more important, the save button is used frequently to keep secure the work done. The more typical case of use for this behaviour would be the edition of a current static article with new info. It´s not like correcting a typo, and a early save could indicate wrongly to the publishers that the article is ready when is not.

Indeed the reviewer maybe ask to approve does it immediately, but then the user will resave and you have a new "revised" version that is pending approval,

in this case this new version will show-up

- in the backend slider of "Revised :: Published, waiting for version reviewal"

- when you filter by STATE in items manager:
"Revised :: Published (Unreviewed Version)"


so our current suggestion is to ask your reviewers to do the above e.g. once per day


we will be adding CRON or pseudo CRON jobs to do tasks, e.g. sending a summary email of items in Pending approval or Revised state could be something to put in the TODO

Regards

I understand now why at first it didn´t send it, I read now "Normally notifications will be sent ONLY (a) once per session for each content item or (b)when its categories are changed"


This means that on the following workflow

New article
Notification sent
Publish article
Modify article
- Here, there would be a second notification implying an update, but it would never be sent, correct?

Maybe we could have a third case (c) "when its state is changed"?

Hello

(c) "when its state is changed"?

changing category is important to justify a second message, maybe changing state is reason to send 2nd message too

we can examine this for v2.2.1

Regards

Friendly bump