06-28-05 10:52 PM
Hi Aby,
you are right, this cannot be achieved.
The reason for this is that there is only one approved version of a posting.
Other versions are historical revisions which are not accessable in
published mode.
So as soon as a new revision is approved the old version is no longer
available in published mode.
In addition to that: the posting properties are not versioned. Means there
is only one start published date which affects all revisions of the posting.
What you could do is to create a copy of the original posting and set the
end publishing of the original one to the same time as the start published
date of the copy.
Then modify the copy.
This will ensure that the original posting will expire the same moment as
the updated version will go live.
There is only one caveat with this approach: links to the posting will break
with this approach.
So if this is not an option you should implement the changes on your staging
system and export the changes to an SDO file. Then run the site deployment
import job at the moment you want to get tha changes live to the production
system.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"A Louis" <ALouis@discussions.microsoft.com> wrote in message
news:52B897C0-2ECD-422B-8B44-773B989AF03D@microsoft.com...[vbcol=seagreen]
> Stefan,
> Let say we have a live posting and the author wants to change the content
> and approve it now. But the author wants the approved content to be
> published
> on the "start date" and current content to be "live" until the "start
> date"
> for the approved content.
>
> I think the way MCMS works, this can't be accomplished. Am I right?
>
> Hope this makes sense.
>
> Thanks,
> Aby
>
> "Stefan [MSFT]" wrote:
>
[ Post a follow-up to this message ]
|