[ckan-dev] Problem with custom fields only new datasets
Nigel Babu
nigel.babu at okfn.org
Thu Jul 3 14:27:09 UTC 2014
Can you point us to the code? It's hard to debug with this much information
:)
Nigel Babu
Developer, Open Knowledge
On 3 July 2014 17:11, Michael Reichart <michael.reichart at gmail.com> wrote:
> 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
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140703/ed3ad404/attachment-0003.html>
More information about the ckan-dev
mailing list