Yesterday, I upgraded finally a plone instance from 4.3.8 to 5.0.4. (ref. MigrationError during plone upgrading from 4.3.8 to 5.0.3). But after a detailed check, compared to a new created instance in plone 5.0.4, I found some strange conditions in the upgraded instance(from 4.3.8) :
1. In the page of @@overview-controlpanel:
(1). There are no icons for caching-controlpanel and dateandtime-controlpanel. But I can access them through the complete url (@@caching-controlpanel and @@dateandtime-controlpanel)
(2). There is a group of “Plone Configuration” in the upgraded instance.
(3). Some items belong to different groups for the upgraded instance and new created instance. There are many difference between the upgraded instance(from 4.3.8) and new created instance
2. In the page of ZMI:manage_main:
(1) Some items exist only in the upgraded instance: uid_catalog (Catalog of unique content identifiers), reference_catalog (Catalog of content references), portal_tinymce, portal_placeful_workflow, portal_metadata (Controls metadata like keywords, copyrights, etc), portal_factory (Responsible for the creation of content objects), portal_discussion (Controls how discussions are stored), portal_atct (Collection and image scales settings), archetype_tool (Archetypes specific settings), portal_undo (Defines actions and functionality related to undo), portal_interface (Allows to query object interfaces), portal_calendar (Controls how events are shown), portal_actionicons (Associates actions with icons)
(2) In the page of portal_properties, imaging_properties (Image handling properties) only exist in the upgraded instance.
(3) In the page of portal_properties/site_properties, there are more items than the new created instance.
What can I do to deal with these difference in the upgraded plone instance and the new created instance(5.0.4)? Is the upgraded instance ready for production use?
Best Regards.
Hugo
