ComponentLookupError: (<InterfaceClass plone.registry.interfaces.IRegistry>, '') after upgrading from Plone 4 to Plone 5

[Farha14]

Hi Team,

We are in process of Upgrading our Plone 4 to Plone 5. We are done with all the code modifications and successfully ran the build out. We initially got the message 'Info: Zope Ready to handle request'. After that when we hit the URL in browser we are getting 'ComponentLookupError: (, '') '. Kindkly refer to the attached logs. Plone_ upgrade_Error_logs.txt

Also when we try to hit the ZMI, we are getting Attribute Error(Portal registry) :

AttributeError('portal_registry',) (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: (, ''))

Our actual motive is to upgrade the Plone 4 to Plone 5.

Please let us know if we can provide you more information.

Thanks &

Regards, Farha

[hvelarde]

what Plone 4 version exactly?

[Farha14]

WE started upgrading our Plone 3.3.5 to Plone 4.0 and it was successfully upgraded after making all the code changes we began to upgrade the Plone 4.0 to Plone 5.0 and here we successfully ran the build and did all the code modifications but now we struck at the above mentioned error

[hvelarde]

Plone 4.0 does not include plone.app.registry by default; you will probably have to install it manually at some point.

[sanjaykapoorsaini]

plone.app.registry is already installed as plone.app.registry-1.3.5-py2.7.egg in buildout-cache. we added plone.app.registry in eggs+= as well as in zcml += in buildout.cfg and rerun the bin/buildout command but there is no impact on result, we are facing same issue.

[hvelarde]

I mean installed in Plone, no present in the buildout.

[petri]

For what it's worth, I get the same exception when trying to rename a Plone 4.3 site I just upgraded to 4.3.15. In my case, the rename triggers indexing in Plone, which in turn calls some third-party code that attempts to get the registry. Really weird that the registry component lookup fails this way.

[pbauer]

Another possible reason is that you uninstalled a addon that had the registry as a dependency. Addons that have the registry as a dependency in metadata.xml (<dependency>profile-plone.app.registry:default</dependency>) will unregister the registry during uninstalling. An example is collective.imagetags.

You can safely remove it by omiting utilities from the the uninstall-cascade like this:

cascade = ['types', 'skins', 'actions', 'portalobjects', 'workflows', 'slots', 'registrypredicates', 'adapters']
quickinstaller.uninstallProducts(['collective.imagetags'], cascade=cascade)

[petri]

@pbauer huh? Thanks for pointing that out. Defaulting to cascading uninstalls seems to me a recipe for disaster, though... Where is that decision made, in zope.configuration?

[jensens]

I close the issue, because it addresses a Plone version that is no longer supported. If you think this is wrong please reopen the issue and assign a matching milestone.