Problems in the caffeinecirculationsystem

1. Migrating is fun fun fun! Let's face it - migrating Plone site from old version to new one can be either painful or very painful experience. If you need to do it for one site only, you don't even get the reward of the fact that second time will be so much easier. Third time you'll start wondering what was the hard part in it. This post is intended to be description how we did plone migration from older version to new one with big, live and heavy traffic site . We're still middle of migrating rest of our sites and therefore I'm going to upgrade this description when I'm having more time. Also note that this is written with one go from memory and as doing the migration is quite complex thing to do including many tasks there might be some errors. I hope this gives some ideas to others struggling with the same topic and also raises some discussion why this is so complex to do when it shouldn't. I'm also happy to get comments how we could have done this be

CMS Wire recently posted a light weight comparsion of open source CMS and their multi-site management capabilities. According to article none of the three popular CMS ( Plone , Drupal and Joomla ) include multi-site management in their core CMS. Article was more about third party addons and what they have to offer for multi-site management needs. Six Feet Up companys Lineage -product shines on this comparsion with it's easy to use separation of certain folder inside Plone site as independet site with certain users, workflows, theme and navigation. Although Lineage is already released it still has some dependencies which are not met with Plone 3.2.1 (but should be in Plone 3.3), so installation needs some additional lines to buildout. You can find more information from Plone Software Center . In the Plone-sites we're developing and maintaining, we've traditionally wanted to keep sites theme pretty much the same within all different departments and faculties. With Lineage