Author: bdaw Date: 2007-03-28 10:48:17 -0400 (Wed, 28 Mar 2007) New Revision: 6866 Modified: docs/trunk/referenceGuide/en/modules/migration.xml Log: small update Modified: docs/trunk/referenceGuide/en/modules/migration.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-28 14:09:08 UTC (rev 6865) +++ docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-28 14:48:17 UTC (rev 6866) @@ -57,6 +57,8 @@ </sect2> <sect2> <title>Database</title> + <note>All things described in this section can be done using AdminPortlet. Treat this directions more as guideline + if you need to automate migration for big portal deployment.</note> <para> Database schema wasn't changed between 2.4 and 2.6 releases, but still content that is kept in it changed slightly in few areas. You can easily update the data manually by using tools proper for your @@ -89,6 +91,7 @@ </listitem> </itemizedlist> </para> + <note>Instead of editing database you can destroy those instances in AdminPortlet and recreate them.</note> <para> <emphasis>NavigationPortlet</emphasis> from JBP 2.4 is not present anymore. Its functionality is now realized by <emphasis>PageCustomizerInterceptor</emphasis> so all references to <emphasis>NavigationPortlet</emphasis> should @@ -112,6 +115,7 @@ </listitem> </itemizedlist> </para> + <note>Instead of editing database you can just remove NavigationPortletInstance using AdminPortlet.</note> </sect3> <sect3> <title>CMS</title>