I have a site with quite a number of pages (several hundred) of which 60 to 70 percent are in "draft" (we are working on an archive and told the client to unpublish the "old" pages). After upgrading to 2.3.2 , it seems we have lost all publication statusses , so all we can do is publish-all pages , or go through the entire sitetree and publish the correct pages by hand.

Is there a way to maintain the publication status while upgrading ?

This happened to the sitetrees of my websites also and made a lot of extra work. But the not working text alignment in the CMS is a much more frustrating factor (http://open.silverstripe.com/ticket/4251).

Does anyone know of a way to prevent this from happening ?

I know I could temporarily put the pages under a different holder etc. , but I hate fiddling with MySQL on Silverstripe databases....

Hi Fuzz,

I haven't seen this issue myself. The publication statuses, ie the colours in the CMS tree, are determined by comparing the contents of SiteTree and SiteTree_Live. Could you look into these tables manually and see if they contain the right content?

If they do, then we have a bug in the colour generation. If this is the case, it would be good if you could help us debug the issue:

The relevant methods are getIsDeletedFromStage(), getExistsOnLive(), and getIsModifiedOnStage() in sapphire/core/model/SiteTree.php

You could add some Debug::message() commands into those and see if you can work out why they're returning the wrong values.

Hope this helps,
Sam

Sam,

Thanks for the reply.

Okay, I had a good look at this yesterday (restoring and upgrading databases) , and have to refine my remarks , sorry about that.

I'm sure it went wrong once (since I still have that database), but I can't for the live of me replicate it ....

Indeed, the publication status draft/published remain intact when upgrading to 2.3.2 , instead, all published pages get the "changed" status (draft pages become "new) .... That is something I feel everyone can live with.....

Odd thing is though ; this happens on our development machine , not in the production environment. Anyway , no biggy ...

Thanks again !