2.0.x to 2.1.x breaks news items if you don't move folder from root! (Was: Plone Migration from 2.1.4 to 2.5.3 breaks news items)

Hi Nick,

Thanks for the follow up email. I just finally finished the migration  
from 2.0.4. to 2.1.4 to 2.5.3 and news items and event items are all  
fine! I was away for a short while and left this migration issue to  
perk for a few days. I then went back to the install guide for  
migration from 2.0 to 2.1 as you have linked below and there is a  
really clear note under the "Common problems and issues" section as  
follows:

If you have an item with the short name events or news in the root of  
your site, they should be renamed before starting the migration -  
since this can cause problems with the migration to the new Smart  
Folders that list these.

Well i started over with a fresh Data.fs (can't emphasize keeping a  
clean backup of what you are trying to migrate) and after bringing up  
under 2.1, i renamed the "news" and "events" folders in the root of  
the plone object. Then i went and did the migration with success. (I  
will someday have to get into the debugging but so far i have  
successfully avoided.)

Also to note, this was a plain vanilla install of Plone so no 3rd  
party items had to be dealt with. There were however a few "custom"  
skin items that had to be renamed so they wouldn't be loaded since  
they were breaking the site and even keeping it from loading in 2.5.  
So thanks for the heads up on that.

On a general issue about migration and news items, when i wound up in  
2.5.3, all the news items were no longer Published. So i had to  
publish them to have them show up. BUT, the act of publishing changes  
the modified date which in turn changes the way they are presented in  
the portal and in the default news item viewer. Was there anything  
that could have been done to have the news items come across as  
already published and the modified date kept the same? Or run some  
python script to publish them all WITHOUT changing the modified date?

Thanks for all the support everyone!

Peace,
Dan


On Oct 1, 2007, at 5:35 AM, Nick Davis wrote:

> Daniel Melnechuk wrote:
>
> > Just found out that news items went south in the migration from  
> > 2.0.x  to 2.1.4. The news portlet would show them BUT when you  
> > click on them  i get the same error as above. So my troubles  
> > actually started in the  migration to 2.1 from 2.0. Maybe i should  
> > try a migration from 2.0 to  2.5? There was something about moving  
> > events and news folders from  root when going from 2.0 to 2.1.  
> > Maybe that is it?
> > Any thoughts? Anyone else ever have news objects go bad on a  
> > migration?
>
> Dan,
>   In case you're still struggling 1 week later, have you thoroughly  
> read this helpful page? :
>
> http://plone.org/documentation/manual/upgrade-guide/version/2.0-2.1
>
> I strongly suggest get the 2.1.4 site thoroughly working before  
> expecting any joy with the 2.1.4->2.5.3 migration.
>
> Common problems include out of date customisations that need  
> recustomising, 3rd-party products that don't play well with the  
> next version of Plone.
>
> Other than that, unfortunately the best thing is to use the  
> debugger to find out why its throwing that attribute error. Google  
> "debug zope". Debugging is intimidating at first but a valuable  
> learning experience. :-)
>
> Regards,
> Nick
>
>
>
> --
> Nick Davis
> Web Application Developer
> University of Leicester
> http://www2.le.ac.uk
>
>
> _______________________________________________
> Setup mailing list
> Setup-G3yHMj00SlOLbbK5bonKug@xxxxxxxxxxxxxxxx
> http://lists.plone.org/mailman/listinfo/setup