make change review and checkin functions more seamless in the GUI

[paregorios]

From @rogerbagnall:

I notice that when I am checking in a copy of a page and click on the option to see changes, there is no obvious route back out of that mode, at least I can't find one. I know that if I click on "view" again the options to check in etc. come back (they vanish during the mode where I see the changes). This is rather weird.

[paregorios]

This will require changes to the default actions for each view, and constitutes overrides of base plone functions.

[skleinfeldt]

@paregorios my notes say that this is a dup...

[paregorios]

Comments copied from #61:

from @paregorios:

Our publications process (workflow) depends on email notifications. Right now, we have the following rules set up:

• email those with publishing authority (i.e., @rogerbagnall) when an item has been submitted for review
• email the creators etc. of an item when it has been moved to "published" status

Our revision process works like this:

• check out working copy (defaults to drafting) of a presently published item
• modify the working copy
• submit the working copy for review (existing content rule mentioned above executes)
• user with publishing authority checks in the working copy, which automatically assumes the published state of the baseline item but doesn't trip the "on publish" rule mentioned above, so the person who modified the item doesn't get an email indicating that it has been published.

There does not seem to be a way to set up a rule to fire on check in.

What can we do?

from @k2soule:

Can we trip a rule to notify the creator of a working copy when that working copy is renamed?

[paregorios]

Doublet for #207

[paregorios]

See also #208