Hi Angus,

No. The cleanup is done using background processing.
Export will always only contain the commited and approved content.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Angus Logan" <angus_logan@data3.com.au> wrote in message
news:O1yK2xxmEHA.3396@tk2msftngp13.phx.gbl...
> Hi All,
>
> I had some strange JavaScript on my page that was breaking the second
> postback (I think) from the authoring page when saving.
>
> My event log has about 10-15 items with "CommitChanges() - Warning: Node d
> not committed or rolled back at start of commit.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp."
>
> I have now fixed the dodgy JS that was preventing the save to complete;
>
> Do I need to clean my MCMS database as I am looking at exporting the
channel
> structure & content and moving it into test (i.e.. will this issue be
> propagated by site deployment?)
>
> Regards
> --
>  ________________________________________

>
> Angus Logan  (MCAD/MCDBA/MCP)
> Lead Software Developer
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
>  ________________________________________

>
>

[ Post a follow-up to this message ]