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

Upgrade from 1.5.0a1 to 3.1 fails #46

Closed
hvelarde opened this issue Dec 1, 2017 · 2 comments · Fixed by #48
Closed

Upgrade from 1.5.0a1 to 3.1 fails #46

hvelarde opened this issue Dec 1, 2017 · 2 comments · Fixed by #48
Assignees
Labels

Comments

@hvelarde
Copy link
Member

hvelarde commented Dec 1, 2017

this happens in Plone 4.3.3:

2017-12-01T00:23:09 ERROR Zope.SiteErrorLog 1512094989.610.449691169693 http://www.example.org/portal_quickinstaller/prefs_reinstallProducts
Traceback (innermost last):
  Module ZPublisher.Publish, line 138, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 48, in call_object
  Module Products.CMFCore.FSPythonScript, line 127, in __call__
  Module Shared.DC.Scripts.Bindings, line 322, in __call__
  Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec
  Module Products.PythonScripts.PythonScript, line 344, in _exec
  Module script, line 11, in prefs_reinstallProducts
   - <FSPythonScript at /Plone/prefs_reinstallProducts used for /Plone/portal_quickinstaller>
   - Line 11
  Module Products.CMFPlone.QuickInstallerTool, line 101, in upgradeProduct
  Module Products.GenericSetup.upgrade, line 140, in doStep
  Module collective.lazysizes.upgrades.v5, line 19, in use_amd_version
  Module Products.ResourceRegistries.tools.BaseRegistry, line 948, in renameResource
  Module Products.ResourceRegistries.tools.BaseRegistry, line 428, in validateId
ValueError: Duplicate id ++resource++collective.lazysizes/lazysizes-umd.min.js
@hvelarde hvelarde added the bug label Dec 1, 2017
@hvelarde
Copy link
Member Author

hvelarde commented Dec 1, 2017

@rodfersou any hints?

@hvelarde
Copy link
Member Author

hvelarde commented Dec 7, 2017

the problem is the following: 1.5.0a1 profile version is 3; in the upgrade step from 3 to 4 we registered the whole jsregistry.xml and it's completely modified leading to a registration of the UMD version and leaving the old non-UMD version registered also.

this breaks the package and needs to be fixed.

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

Successfully merging a pull request may close this issue.

1 participant