Updating plone

Plone 5 will introduce some new concepts, for some, with working with Java Script in Plone.

updating plone-27

Generic Setup-1.8.0-py2.7.egg/Products/Generic Setup/upgrade.py", line 166, in do Step self.handler(tool) File "/usr/local/Plone/buildout-cache/eggs/upgrade-1.3.18-py2.7.egg/plone/app/upgrade/v50/betas.py", line 63, in upgrade_portal_language lang_settings.use_content_negotiation = portal_languages.use_content_negotiation Attribute Error: use_content_negotiation Starting upgrade of core addons. End of upgrade path, migration has finished The upgrade path did NOT reach current version Migration has failed Dry run selected, transaction aborted Key Error('Interface `Products. ILanguage Schema` defines a field `available_languages`, for which there is no record.',) (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: Interface `Products. ILanguage Schema` defines a field `available_languages`, for which there is no record.) 2015-10-09 INFO upgrade Dry run selected.2015-10-09 INFO upgrade Starting the migration from version: 4311 2015-10-09 INFO upgrade Ran upgrade step: Miscellaneous 2015-10-09 INFO Products.Getting back on point, much of Plone's Java Script was or still is using Java Script in a non-AMD form.Scripts that expect Java Script dependency scripts and objects to be globally available and not loaded synchronously will have a difficult time figuring out what is going on when upgrading to Plone 5.It provides a control panel for running multiple upgrades at once, based on the upgrade mechanism of Generic Setup (portal_setup).

Further a base class for writing upgrade steps with a variety of helpers for common tasks is provided.

Generic Importing profile upgrade.v50:to50alpha3 with dependency strategy upgrade. Generic Applying main profile upgrade.v50:to50alpha3 2015-10-09 INFO Generic Setup.rolemap Role / permission map imported. CMFCore-2.2.10-py2.7.egg/Products/CMFCore/Directory View.py:493: User Warning: Directory View plone_deprecated refers to a non-existing path 'Products.

CMFPlone:skins/plone_deprecated' (self.id, reg_key), User Warning) /usr/local/Plone/buildout-cache/eggs/Products. CMFCore-2.2.10-py2.7.egg/Products/CMFCore/Directory View.py:493: User Warning: Directory View plone_styles refers to a non-existing path 'Products.

The above statement is the easiest and will work in all Plone versions; previously a more fancy statement with a condition was advocated, which we will give here for good measure: From Plone 4.1 on, versioning policies for custom types can be configured using Generic Setup (repositorytool.xml).

This document covers the procedures and issues involved in upgrading an existing Plone installation.

We chose AMD over other module loading implementations(like commonjs) because AMD can be used in non-compiled form in the browser.