[ckan-dev] Problem with custom fields only new datasets

[Qifeng.Bai at csiro.au]

Are you using ‘extra fields’ as well?  -  you can add /delete those fields

If you are using ‘extra fields/’, then the custom fields won’t work.  That is my understanding

From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] On Behalf Of Michael Reichart
Sent: Thursday, 3 July 2014 9:42 PM
To: CKAN Development Discussions
Subject: [ckan-dev] Problem with custom fields only new datasets

Hi,

we have added serveral custom fields in our datasetform and adapted the schema like described in the docs.Everything works fine when we are saving an existing dataset - all custom fields are correct mapped and stored.

But if we create a new dataset some of the fields (6 of the custom fields, everytime the same ones) are not getting stored. These fields are located at the 3rd step of creating a new dataset (after uploading/linking a resource). There are other custom fields in this step which are working perfectly.

Any ideas what the problem could be? I even tried to implement the function "new metadata" in a custom package controller. It seems like the data is correct in the data_dict before updating the dataset, but the fields are missing in the object returned from get_action(package_update)...

We're using CKAN 2.2

Thanks!

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140703/438a10f2/attachment-0003.html>