Open petschki opened 6 years ago
after some more investigations I've found out, that Products.CMFDefault is no dependency in Plone>=5 anymore and therefore is unpinned in versions.cfg. That's why I've got CMFDefault==2.3.0b2 which isn't compatible with CMFCore. I'll try to find out, where CMFDefault gets a dependency here ...
PS: quickfix for anyone who uses a fresh Plone>=5 buildout is to pin Products.CMFDefault==2.2.4
I too want to use this add-on with 5.1-latest. I got Products.CMFDefault==2.2.4
, so my trouble only started when going to run the quickinstaller. When I try to install on a site, I get a traceback, and some detective work led me to find this issue and PR #62. That commit (on master) makes it go again, so the question that begs to be asked.... when will 3.4.9 be released?!?
Well, I guess there are still other issues that need to be fixed to make this add-on work with 5.1.x
. For example, I discovered that having this add-on installed in an otherwise a stock traning_buildout
causes all of the ++add++
forms to appear empty. Removing it from buildout.cfg
restores those forms. This add-on is referenced explicitly in the Mastering Plone training module, so these bugs create a bit of a bump in that learning curve.
Could you file an issue in the documentation repo for this?
@zachwelch sorry for that. The issue with empty ++add++
forms is due to this issue: https://docs.plone.org/develop/addons/upgrade_to_51.html#cmfdefault-removal
I've added version 3.4.8 to a fresh plone 5.1-latest buildout and get this traceback when starting the instance:
when I remove the
collective.plonetruegallery
line from the eggs, everything works fine. Maybe an issue with theinstall_requires
of setup.py?