Closed fulv closed 9 years ago
@fulv I cannot reproduce the issue. I create new site using the buildout of plone.app.contenttypes and he migration worked. Will repeat the test with the unified installer for 4.3.5. Which buildout did you use?
@fulv same is true for the unified installer: the migration works. I pinned plone.app.event like this to not get p.a.widgets:
plone.app.event = <= 1.1.999
I used the ansible buildout, but I did have widgets. I'll try again without.
On Fri, 29 May 2015 03:23 Philip Bauer notifications@github.com wrote:
@fulv https://github.com/fulv same is true for the unified installer: the migration works. I pinned plone.app.event like this to not get p.a.widgets:
plone.app.event = <= 1.1.999
Reply to this email directly or view it on GitHub https://github.com/plone/plone.app.contenttypes/issues/230#issuecomment-106766777 .
@fulv can we close this or could you reproduce it?
I tried it again on 4.3.6, and could not reproduce (even though I had p.a.widgets, because I forgot to pin plone.app.event = <= 1.1.999).
I have installed a brand-new Plone 4.3.5 site with plone.app.contenttypes = 1.1b4. When doing the migration of the default content, I get the following: