-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can't import settings from registry.xml in v0.7.2 onwards #14
Comments
Upgrading to latest plone.supermodel (1.2.6) doesn't fix it. Removing the
Which looks like plone.supermodel has found the wrong converter.... |
Adding a value_type to the field in registry.xml seems to make the import work, but unfortunately the just ends up with a This means that the exporthandler is also wrong somewhere as it should set a value_type Setting value_type to
My registry.xml now looks like this:
|
I'm going to leave this here for now and just pin to 0.7.1 of collective.cookiecuttr. The issue is almost certainly within collective.z3cform.datagridfield, but perhaps we could use an alternative? Does anyone have the GS import working since 0.7.2 ? |
Still an issue don't know whether this is maybe to do with me using plone.app.contenttypes on Plone 4.3 |
Sorry... No, I haven't seen this problem before, but we didn't try to save the information in the GS profile and then import back. |
Thanks for the reply. If this isn't working, would you agree that we may need to rework the |
Yes, or at least the import/export steps. |
Ok, yes - I figure the export is wrong somehow, so that's the first |
No idea, but to be honest we havent used the package for years now :) |
Using this registry.xml
I get the following error
I believe this is the same issue mentioned in collective/collective.z3cform.datagridfield#22
The text was updated successfully, but these errors were encountered: