Ticket #11640 (confirmed Bug)
Upgradestep "Uninstall a broken CacheFu" does not remove caching_policy_manager, portal_squid, etc
Reported by: | frisi | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 4.x |
Component: | Upgrade/Migration | Version: | 4.0 |
Keywords: | Cc: |
Description
when upgrading a 3.3.5 site to 4.0.4 one of the steps that should be run is:
(all → 4001)
- Uninstall a broken CacheFu
however, after upgrading the site, portal_cache_settings, portal_squid, et al are still around on my plonesite as broken products (Broken Because Product is Gone)
the handler plone.app.upgrade.v40.alphas.removeBrokenCacheFu checks if portal.caching_policy_manager is a broken object and only deletes all the tools in this case. on my site caching_policy_manager is of type Products.CMFCore.CachingPolicyManager and not broken.
maybe at the time this upgrade step has been written, CMFCore did not ship with that?
Change History
comment:3 Changed 3 years ago by frisi
currently i don't have a plone 3 site (with cachefu installed) around where i could easily try an upgrade to 4.2
if the uprade step still only checks if the tool caching_policy_manager is broken the problem most probably still exists as in my case this the tool has been provided by CMFCore.
we could close this bug and wait for another and more recent report and reopen it in this case. very likely this will lead to a separate report however.