v0.4 migration notes for mycopart ploneboard
ploneboard updates
0. Make backup of the production Data.fs and other files at:
/opt/mycopart/Plone/var/filestorage
1. in the production ZMI quickinstaller uninstall copart.Ploneboard
2. in production move the old egg... Products.copart.Ploneboard-v0.3a-py2.4.egg to a safe place.
3. copy Products.mycopart.Ploneboard-v0.4a-py2.4.egg from the stage instance.
4. replace Products.copart.Ploneboard with Products.mycopart.Ploneboard in the buildout cfg file... mycopart_base.cfg
5. rebuild
6. restart
7. in the production ZMI quickinstaller install mycopart.Ploneboard
8. In the production ZMI go to /portal_skins/tinymce/tiny_mce_init.js click the customize button
9. copy the text from stage /portal_skins/custom/tiny_mce.init.js to production /portal_skins/custom/tiny_mce.init.js
10. In production /portal_javascripts/ move tiny_mce_init.js and tiny_mce.js scripts to just below the JQuery scripts by clicking on
the up arrows. tiny_mce_init.js should be first.
11. test to see if the editor works properly from the "idea" view and the "reply" view
Deliverance updates
0. In prod make a backkup copy of theme_mycopart.html and delverance_mycopart.xml
1. In prod checkout the theme_mycopart.html and delverance_mycopart.xml and replace existing ones.
2. restart deliverance
3. test
plone main_template & login_form update
1. in production ZMI go to /portal_skins/custom and check if main_template or login_form is in custom folder.
2. if no templates go to /portal_skins/plone_templates and copy
the main_template into custom folder by entering the customize button.
Do the same for the login_form in /portal_skins/plone_login.
3. Replace the text from /portal_skins/custom/main_template and /portal_skins/custom/login_form in Stage to Production and save.
4. Test links. When clicking on the "Need help logging in" link a alert box will pop up. When closed by the user the browsed page should be reloaded.
note1: This took me about 1/2 hour to do from dev to stage
note2: On a recent build Xron caused problems by calling a non-existent method in ZOEB may need to comment it out in the buildout config files.
