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

Avoid registering static resources on registries #820

Open
hvelarde opened this issue Aug 27, 2018 · 1 comment
Open

Avoid registering static resources on registries #820

hvelarde opened this issue Aug 27, 2018 · 1 comment

Comments

@hvelarde
Copy link
Member

hvelarde commented Aug 27, 2018

The revolutionary approach chosen for Plone 5 resource registries rewrite makes difficult to maintain single add-on versions that work in both Plone 4.3 and latest Plone 5:

  • some of the JavaScript tools used (Bower, Grunt, RequireJS…) seem to be less attractive nowadays than more modern options (webpack)
  • Resource bundling was a workaround for a limitation of the HTTP/1.1 protocol and not a CMS feature; HTTP/2 makes it unnecessary and even undesirable

Getting rid of the resource registries registrations will make upgrades much easier.

refs. plone/Products.CMFPlone#1896
refs. #819

@idgserpro
Copy link
Member

I think #613 can be closed when this is finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants