Hi,
I think it would be easier to have staging server separate from production
one. You can edit objects on staging server and upon approval syndicate
them to production. That way you keep object ID's the same and archive
them easily.
Mark Feldman.
Web Developer.
UniSuper Limited.
>>> [EMAIL PROTECTED] 09/10/01 01:32pm >>>
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
