Seth,
We make our edit handlers always edit the most recent version. Then when
writing the changes create a new version, get the the property versionid for
that version (It'll be the one at array position 1 in the versions).
Versionid is the actual objectid of the version. You can then use codata to
write to the top version without changing the published object.
When you want to make your changes live, grab the most recently edited
version (array pos 1 again) and use codata to write it to the actual object
this time.
HTH,
Andy
> -----Original Message-----
> From: Seth Hodgson [mailto:[EMAIL PROTECTED]]
> Sent: 10 September 2001 04:32
> To: Spectra-Talk
> Subject: staging content
>
> 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.
