|
Greetings,
I'm trying to build a content staging system for
versioned content objects that would allow for edits to an existing object
without effecting the objects version history unless the edits were approved by
an administrator. To do this, within my edit handler I am generating a new co
with matching properties (including the label which is unique per co) and
setting it's active and archived flags to false. This is the object that is used
to store edits to the corresponding live co (matching labels). Upon approval of
the edit, a new version of the true content object is created and the live
version is updated with the edited content - lastly, the edit co is
deleted.
Is there a simpler way to go about
this?
Best Regards,
Seth
|
- Re: staging content Seth Hodgson
- Re: staging content Mark Feldman
- RE: staging content Robin Hilliard
- RE: staging content Mark Feldman
- RE: staging content Andy Fletcher
