Can Revo allow staging of content?

MODX is great and there is nothing wrong using other CMS's if MODX doesn't do what you need it to at least there are other options

Good Luck.

Is the goal to do this across remote MODX deployments (i.e. staging vs. production)? Or are you only looking to "stage" new Resources created by this User Group within a single production MODX deployment?

Quote from: opengeek at Jun 28, 2013, 12:31 PM

Is the goal to do this across remote MODX deployments (i.e. staging vs. production)? Or are you only looking to "stage" new Resources created by this User Group within a single production MODX deployment?

The Goal is to have one MODx deployment which includes the facility for new and published resources to have 'staged versions'. E.g. A resource could be live, but then a MODx user can log in and make a new version of said resource and make changes and save it as a 'draft' version which does not go live, but has the option to be published to replace the current live version if the user decides so.

Basically I am after a way that the CMS users can create new versions of the same page with different content etc to test new ways of presenting content within the site or just updating content which then needs review by another person.

So rather than just being able to hit SAVE on the resource and have an option of PUBLISHED or NOT PUBLISHED, there would need to be included a version history of 'versions' of the resource that had been created with the ability to publish any of these versions, update them, or delete them.

I am going to review how SilverStripe do it now and will report back and see if we can work out a way of emulating something similar if it works well. Looking here this summarises it quite well > http://www.silverstripe.org/cms-workflow-module/

Silverstripe allows the content editor to save a draft version of a page - it then also has a history list of drafts for each page which the user can view and publish as they chose - this works well and is a simple approach - i know VersionX kind of does this... but it's over complicated and unintuitive I find...

Going to install the CMS Workflow addon now and will report back about that also... Seems SilverStripe also has this advanced workflow which looks good > http://www.silverstripe.org/advanced-workflow-module/ [ed. note: dubbs last edited this post 13 years, 3 months ago.]

Guys - have a look at this doc from SilverStripe - articulates the workflow very well in the first few pages > http://silverstripe.jonwallacedesign.biz/cmsworkflow/doc/Silverstripe-CMS-Workflow.pdf

Guys - see this diagram from an example of how I would like the workflow solution to work:



Is this possible?

Certainly possible; you'll just need some code to handle those features and somewhere to store the drafts. I was thinking this would be easy to accomplish using a the registry API. Drafts can be stored in a topic and retrieved, previewed, and approved/rejected from those messages. They could be stored as diffs or full versions in the topic messages.

Quote from: opengeek at Jul 01, 2013, 07:22 AM

Certainly possible; you'll just need some code to handle those features and somewhere to store the drafts. I was thinking this would be easy to accomplish using a the registry API. Drafts can be stored in a topic and retrieved, previewed, and approved/rejected from those messages. They could be stored as diffs or full versions in the topic messages.

Great - sounds good Jason, is this something anyone would like to take on? I do not have the PHP/Core framework skills to undertake this but would love to get it sorted...

They key here is being able to save a resource as a draft version as you say, then having a live and a draft version of each resource - and the ability to switch the live version from one to the other easily. Saving a new resource or updates to a published resource by an editor would create a new draft and notify the publisher of this action. If someone can take this on, I can fully brief them with the requirements...? Anyone??? [ed. note: dubbs last edited this post 13 years, 3 months ago.]

Hi guys - Core MODx team - any updates on the likelihood that staging of content will be included in a future MODx release sometime soon?

Anybody interested in taking this on as a commissioned piece of work perhaps?

I've just begun work on a revision management tool called Revise that will initially provide simple support for managing future Drafts and saved History of Resource objects. You will be able to view and/or apply the Draft/History objects, and configure how many/often/long they are kept. We will then start adding support for various roles to participate in a publishing workflow using these tools and/or support for tracking revisions of various other objects in MODX.

Note, my initial version in development does not persist Resource related data such as Template Variables. It uses them as they are, only saving snapshots of the Resource itself as a Draft/History object. The ability to manage related data may also be added in the future.

If you are interested in participating in the development of this Extra (as a user, developer, or documentor), please contact us at support at modx dotcom to let us know.

Quote from: opengeek at Jul 23, 2013, 08:36 AM

I've just begun work on a revision management tool called Revise that will initially provide simple support for managing future Drafts and saved History of Resource objects. You will be able to view and/or apply the Draft/History objects, and configure how many/often/long they are kept. We will then start adding support for various roles to participate in a publishing workflow using these tools and/or support for tracking revisions of various other objects in MODX.

Note, my initial version in development does not persist Resource related data such as Template Variables. It uses them as they are, only saving snapshots of the Resource itself as a Draft/History object. The ability to manage related data may also be added in the future.

If you are interested in participating in the development of this Extra (as a user, developer, or documentor), please contact us at support at modx dotcom to let us know.

Thanks opengeek - sounds good, I would think including the TVs in the draft versions is pretty vital as lots of page content is always held in TVs particularly in the way I utilised MODx for websites... I'd love to help test / scope out and work with you on this. I will drop you a mail now.

Cheers,
dubbs.