Can Revo allow staging of content?

Understood regarding TV's; that process is just a lot more complex for several reasons (especially being able to view the revisions) and we had a requirement to get it working with just the Resource data. Thus, that will be the first iteration.

Quote from: opengeek at Jul 23, 2013, 09:01 AM

Understood regarding TV's; that process is just a lot more complex for several reasons (especially being able to view the revisions) and we had a requirement to get it working with just the Resource data. Thus, that will be the first iteration.

100% understood - getting it working well with the base Resource 'content' field will be a good start - then bringing in support to allow the same for TVs will be great. I don't personally see a need to have granular 'versions' of each TV / content field within a resource, it's more like a version of the resource - with all related data being included in each version. Does that make sense?

Right, the current problem is simply making sure the snapshots of the TV data are used by the core and any Extras on the Resource when it is processed for (pre)viewing.

I would just like to lend support to this as a "killer" feature. I realise that there are technical challenges to achieve but it was promised right back in the initial blog post launching Revo so I'm certain that it can be achieved with the architecture.

I understand that such projects are very labour intensive and that this is often challenging to achieve for an open source project - happy to look at contributing to any type of funding initiative on this to keep it moving.

Is there anything we can learn from VersionX for this? Is it essentially the same functionality, but with an additional flag stating what version of an element is "current". I can see that the Core would need an update to reflect this flag but hopefully this is the purpose behind a solid Service orientated API?

Will certainly be signing up to support user testing.

Cheers,

Steve

Quote from: DangerMouse1981 at Jul 23, 2013, 10:28 AM

I would just like to lend support to this as a "killer" feature. I realise that there are technical challenges to achieve but it was promised right back in the initial blog post launching Revo so I'm certain that it can be achieved with the architecture.

I understand that such projects are very labour intensive and that this is often challenging to achieve for an open source project - happy to look at contributing to any type of funding initiative on this to keep it moving.

Is there anything we can learn from VersionX for this? Is it essentially the same functionality, but with an additional flag stating what version of an element is "current". I can see that the Core would need an update to reflect this flag but hopefully this is the purpose behind a solid Service orientated API?

Will certainly be signing up to support user testing.

Cheers,

Steve

Thanks for lending your support Steve - agreed, this is really a must-have for future MODx builds - something that is integral to a CMS solution for larger organisations and something I am really excited about assisting in getting shaped and created for MODx.

I've opened the repository for participation at https://github.com/modxcms/Revise/issues

Questions are welcome at this time, though this is not even in shape yet for an initial beta release for general testing, but any developers that want to participate and can build the Extra from source are welcome to fork or just take a look.

I plan to have a beta release in the Extras repository when we hit the v1.0.0-beta milestone.

Quote from: opengeek at Jul 26, 2013, 12:07 PM

I've opened the repository for participation at https://github.com/modxcms/Revise/issues

Questions are welcome at this time, though this is not even in shape yet for an initial beta release for general testing, but any developers that want to participate and can build the Extra from source are welcome to fork or just take a look.

I plan to have a beta release in the Extras repository when we hit the v1.0.0-beta milestone.

Hi Opengeek - any updates/news on the REVISE plugin? I have a live project coming up where I will need tiered user roles with ability to create draft versions of both published and unpublished resources...

I'd appreaicate an update on the status of this plugin if that's possible?

Cheers,

dubbs.

It's functional enough to power our new RTFM, but I have not made any progress on it since we released. Instead, I've been focused on finishing up 2.2.9 and preparing 2.3 releases. I should have some time next week to get back on Revise.

Opengeek, has there been any more recent progress with Revise. It sounds like the exact thing that I will need with a big corporate site I have coming up soon or is Revise being rolled into 3.0.

Quote from: glynszasz at Feb 08, 2014, 04:06 AM

Opengeek, has there been any more recent progress with Revise. It sounds like the exact thing that I will need with a big corporate site I have coming up soon or is Revise being rolled into 3.0.

Id love to know about the current status too. Revise (or similar, e.g. version control of resources and TV data, plus ideally chunks / snippets / templates as well) is something vital to future MODx versions I think - it's where MODx is let down vs something like WP