Fair enough, but we seem to have drifted away from the original topic here, the OP didn’t want versioning he wanted promotion from one server to another and associated management thereof are we saying we can do this now(when implemented obviously) and can we sync databases together, from backups, external systems?. A number of posters have suggested versioning schemes that would work albeit IMHO sub-optimally but are valid all the same.
I can’t install transport packages into non-revo environments but I can install my data, suitably tagged I can move it around and audit it, from source, to revo to backend historying to evental archive storage in possibly NOSQL databases, uniquely.
I view Revo as a portal(the best) through which people view my data, not the custodian of it, data moves and morphs around these days, tracking it, analysing it and storing it are just as important if not more so than viewing it.
I don’t wish to thrash a dead horse here so I’ll wait for the proposed solution to this.
Use MODx, or the cat gets it!
Just want to add this here:
I have had clients creating resources set unpublished = they can preview the pages logged in.
Then have had another manager with the rights to publish the resources or even better publish after
duplicate them to another restricted folder so they still can edit the unpublished resources.
