Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundles switch while upgrading from 2.2.X to 3.0.X #69

Closed
wants to merge 3 commits into from

Conversation

yurj
Copy link
Contributor

@yurj yurj commented Jan 11, 2024

Upgrading removes the patternslib bundle but does not add the new bundle.

Upgrading removes the patternslib bundle but does not add the new bundle.
@yurj yurj requested review from petschki and laulaz January 11, 2024 14:38
@yurj
Copy link
Contributor Author

yurj commented Jan 11, 2024

Works on a local instance. But this:

  <records interface="Products.CMFPlone.interfaces.IBundleRegistry"
           prefix="plone.bundles/bundle-leaflet"
           remove="true"
  />

doesn't remove the patternslib leaflet bundle. It is Plone 6.0.0a2, so maybe there are some leftovers but the registry entry is prefix plone.bundles/bundle-leaflet and interface IBundleRegistry. Oh, I found out. In Plone 6.0.0a2 the interface is Products.CMFPlone.interfaces.resources.IBundleRegistry. It is correct and consinstent with Plone 5.2-latest:

https://github.com/plone/Products.CMFPlone/blob/5.2.x/Products/CMFPlone/interfaces/resources.py

class IResourceRegistry(zope.interface.Interface):

So I think we should change Products.CMFPlone.interfaces.IBundleRegistry to Products.CMFPlone.interfaces.resources.IBundleRegistry too.

Locally, this works and the upgrade remove the leaflet bundle and install the plone.formwidget.geolocation/bundle-remote.min.js one.

@petschki @laulaz do you agree?

Products.CMFPlone.interfaces.IBundleRegistry to Products.CMFPlone.interfaces.resources.IBundleRegistry
@laulaz
Copy link
Member

laulaz commented Jan 12, 2024

@yurj as the 3.0.x versions are not compatible with Plone 5 anymore, shouldn't we use the "non-deprecated" plone.base.interfaces.IBundleRegistry interface for the bundle registration ?

@yurj
Copy link
Contributor Author

yurj commented Jan 12, 2024

@yurj as the 3.0.x versions are not compatible with Plone 5 anymore, shouldn't we use the "non-deprecated" plone.base.interfaces.IBundleRegistry interface for the bundle registration ?

I've used what appears on the menu dropdown in the configuration registry under "IBundleRegistry", I think this interface path is well supported until Plone 7.0. This can help also to migrate from and in old Plone instances? I'm not an expert so i rise my hands on this.

For uniformity, use `Products.CMFPlone.interfaces.resources.IBundleRegistry` also here.
@petschki
Copy link
Member

Is this still needed? a lot has changed since 6.0a and I'm not able to reproduce this scenario ... though the interface should be changed to plone.base indeed. I'll create a separate PR for that.

@yurj
Copy link
Contributor Author

yurj commented Aug 27, 2024

If not reproducible, it is better to close this PR.

@yurj yurj closed this Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants