Upgrading from Plumi 0.2.2-final to Plumi 0.2.3-final
-----------------------------------------------------

1) Please read this ticket about upgrading Indytube
http://plumi.org/ticket/204

The names of the Indytube-produced HTML files containing the FlowPlayer code for video playback in the browser have changed.

2) Reinstall ATVideo and PlumiSkin products. 

3) Use the archetypes tool->Update Schema tab in the ZMI to update any archetypes objects whose schema has changed. This could take a very long time, be patient. You can check back on the page (if it timeouts out) and see if all the check-boxes that were automatically checked, have been unchecked. This means the process has finished.

4) Use the portal catalog->Advanced in the ZMI to 'Update catalog', or 'clear and rebuild' - 
however 'clear and rebuild' will remove the recent comments listing in the recent comments portlet on the front page 
(not the comments itself though)


Upgrading from Plumi 0.2-final to Plumi 0.2.2-final
---------------------------------------------------

Use the quickinstaller to reinstall ATVideo and PlumiSkin

Use the archetypes tool->Update Schema tab to update any archetypes objects whose schema has changed. This could take a very long time, be patient. You can check back on the page (if it timeouts out) and see if all the check-boxes that were automatically checked, have been unchecked. This means the process has finished.

Use the portal catalogue to 'clear and build'. This may take a very long time also.

If there are repeated top-level tabs  ("Review List", "About Us" etc) , go into portal_actions are delete the duplicates.



Upgrading from Plumi 0.1-final
------------------------------

If you are moving your plone instance to a new location (even within the same server) you need to update the objects notion of where
the externally storied video files are, see MOVING INSTANCE below to do this first.

UPGRADING PLUMI

** There was a bug on the members preference form, such that if a member used this form, they would be no longer included in members search listings.
If you want to update your members, so that the installer for PlumiSkin re-adds them to the search listings, you need to change
PlumiSkin/config.py, variable UPDATE_USER_LISTED_IN_SEARCHES, to True. 
By default, this is set to False, that is, it will not check your members on re-installing.
Make sure after you have set this True, and re-installed the product, you set it back to False, to avoid updating members, who could of 
validly opted-out of search listings **


Upgrading the Plumi site within ZMI: 
	1.Uninstall TagCloudExplorer
	2.TagCloudExplorer doesnt completely uninstall properly, so you will need to go into the portal_skins and remove all references
	to the skin name - tag_cloud_explorer
	3.Remove "here/portlet_tag_cloud_explorer/macros/portlet" from the right_slots in your plone site properties tab 
	4.Reinstall PlumiSkin and ATVideo via the quick_installer.
	5.Use archetypes tool to upgrade the schemas on the objects. 
	6.Upgrade Plone version - atct tool, portal_migration 
	7.Reinstall products that have upgrades. (ATVocabularyManager etc)
	8.Clean and Rebuild Catalog.

MOVING INSTANCE

-- only do this if you are changing the location of the plone instance on the filesystem!! --

Start the plone instance in debug mode (./bin/zopectl debug)
Make sure you know the new location of the plone instance on the filesystem, and the name of the plone site in the zodb.

	Find the script move_ES.py in the ATVideo product. 

	You will need to change the line 12, to rename from "Beta" to the
name of your plone instance.
	You will need to change line 15, to set NEWROOT to the new location of the plone instance

	Copy and paste this script onto the python console that starting the plone instance in debug mode has shown you.

	Make sure you do the last two lines of the move_ES.py script - that is, committing the transaction to zodb. They are commented out
	to avoid mistakes , if you havent configured things properly.

