Thanks Nick for this email. I have close to 15+ third party products installed in Plone but I am not sure what are being used in Plone 2.0.5. Is there any way to find this out? Also, what would be the best way to find out if these products are compatible with 2.5 or 3.0 versions of Plone? The list of products which I was able to gather are these:
BTreeFolder2 CMFQuestions DocFinder DocFinderTab Epoz ExternalFile Formulator generator IssueTrackerProduct NauScheduler NuxDocument PloneLocalFolderNG PloneSiteMap PloneWeatherForecast PortalTransforms WeatherReport Workgroup ZMySQLDA ZSyncer Basically, I did a comparision of Products directory in 2.0.5 and 2.5.5 and listed only unique ones (ones where were not present in Products directory of 2.5.5). Is this the correct approach? Let me know. Thanks again, Rohit Nick Davis-3 wrote: > > peyyetir wrote: >> Hello, >> >> Need some help in upgrading Plone from 2.0.5 to 3.0. I belive that >> upgrade >> from 2.0 to 2.1 is a major upgrade. I just wanted to know if I can >> upgrade >> from 2.0.5 to 3.0 directly or do I have to upgrade from 2.0.5 to 2.1 to >> 2.5 >> and then 3.0. Which path would be a better option? Can somebody provide >> some >> pointers here? >> >> If anyone has done the upgrade from 2.0.5 to 3.0, please let me know. >> > > > Rohit, > 2.0 to 3.0 is a lot in one go, and hardly anyone has done that all at > once. If something goes wrong it might be hard to know where. On the > other hand, branding of 3.0 is so much easier and nicer than 2.1 or 2.5, > that it makes sense to go straight to 3.0, rather than waste time doing > re-branding on 2.5 for example. > > The main things you'll have to fix are : > a) Customisations which may no longer work in versions later than 2.0 > b) Third-party products that have not kept up-to-date well with Plone. > > The more your site is customised, the more messy this migration could > be. It's probably best in your situation to "throw away" existing > customisations, just migrate content, and re-brand from scratch. > > I recommend do 2.0 to 2.5 on a test machine and get it working (minus > customisations, in an unbranded state) first before trying to go to 3.0. > Try to test throughly and make sure there are no problems with the 2.5 > site. If you do encounter problems here, at least you know it was > between 2.0 and 2.5 (probably between 2.0 and 2.1, because thats the > more difficult/messy step). Keep this system intact, so that if problems > occur on 3.0, you could go back later and check whether the same problem > existed at 2.5. > > More info on the 2.0-> 2.1 step : > http://plone.org/documentation/manual/upgrade-guide/version/2.0-2.1 > > Hope this helps, > Nick > > P.S At some points during this migration you may feel fairly, er, > "brain-fried", and start wishing you'd never chosen Plone. ;-) However, > this feeling will not last forever! ;-) It is worth the effort because > the later versions are a huge improvement on 2.0, and easier to work with. > > -- > Nick Davis > Web Application Developer > University of Leicester > http://www2.le.ac.uk > > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > > -- View this message in context: http://www.nabble.com/Plone-Upgrade-tp16191756s15482p16327203.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
