You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Abstract

This concept belongs to the BL-127 "As a user I can activate content so that it gets published" story. The goal is to allow users to activate/deactivate the content. ATM, the legacy commands from the Admin Interface legacy module will be used.

Goal

The goal is to allow users to activate/deactivate the basic content (pages, assets, contacts(question)) from author to public instance(s), and to show developers the way to provide this functionality for their own content types.

The solution must be flexible and allow dynamic replacing of the behavior, e.g. by the workflow modules.

Proposal

Activation / Deactivation commands from the (old) admin interface module will be moved to the new admin-interface-legacy module and used to do the back-end work.

The Activation / Deactivation actions will be created and linked to proper buttons in the action bar of required apps.

 

  • No labels