workflow: editors and supervisors groups

[YoJoe]

hello
I've been wondering for quite some time if there is a way to achieve a simple workflow schema, where editors group write articles, but cannot publish them. But once they finish creating an article (news, page, article etc.) they somehow (for example clicking a dedicated button) let know users from supervisors group, that they may review the article, and approve it or reject it. Until then article would remain unpublished/hidden.



Such simple workflow seems to be a rare functionality of GPL CMS-es, and if it is available, its overall usability is very complicated.

[Stefek]

This is not part of the News Module,
however, this is not too hard to achieve - just some of the code must be reworked, that only the superadmin may be able to activate/deactivate Posts.

Or do you mean all websitebaker pages, not specifically for the news module?

Regards,
Stefek

[DarkViper]

... finish creating an article (news, page, article etc.) they somehow (for example clicking a dedicated button) let know users from supervisors group, ...

Till now that is not possible yet. The rights system of WB is based on whole pages and not on sections or articles.
To delegate this job to the different modules is not userfriendly, because each of the module authors will implement his own solution and so there is no consistent workflow over all.

For sometime in the future it is planned to expand the rights system for sections and maybe entries in modules too. Then your requirements can be fulfilled.

My idea for a good workflow is:

• a editor can create and modify a new article using a defined number of modules (wysiwyg, news, topics, and more), but never he can activate his article.
• after he finished work, he can click a 'Request for activate'-button which sends a message to the admin
• the admin(s) can switch the article to 'activated' and in the same time switch the editors right to readonly, to prevent uncontrolled, additional changes.

[YoJoe]

Till now that is not possible yet. The rights system of WB is based on whole pages and not on sections or articles.
To delegate this job to the different modules is not userfriendly, because each of the module authors will implement his own solution and so there is no consistent workflow over all.

For sometime in the future it is planned to expand the rights system for sections and maybe entries in modules too. Then your requirements can be fulfilled.

My idea for a good workflow is:

• a editor can create and modify a new article using a defined number of modules (wysiwyg, news, topics, and more), but never he can activate his article.
• after he finished work, he can click a 'Request for activate'-button which sends a message to the admin
• the admin(s) can switch the article to 'activated' and in the same time switch the editors right to readonly, to prevent uncontrolled, additional changes.

This is exactly shortest path how such workflow should work
Anyway I understood that WB isn't - and won't be for quite long time - capable of fulfilling such functionality.
From one hand it's a pity, as it could expand to mid-large market, where advanced user/group rights are basic requirements.

Thx for answers gentlemen.