Ian Ward
Ian Ward
That's very strange! I'll see if I can reproduce the error you're seeing.
In ckan the package_update method takes both "tags" and "tag_string" values and converts the "tag_string" to "tags" inside the action, so the next time the dataset is updated the "tag_string"...
The `scheming_multiple_choice_output` validator is installed when you enable one of the scheming plugins. What plugins are enabled on your site?
which version of ckan and which version of ckanext-scheming are you using?
scheming may just be incompatible with 2.8 right now. We'll need to investigate. @amercader are you aware of any sites using scheming with 2.8?
@shevron Thank you for that. The defensive validator check was for supporting ckan versions before 2.8 where we weren't allowed to redefine validators. We can either fix the defensive check...
Please open separate issues or PRs for 1, 2, and 3, this one is just for per-field validation of multiple_text. I'm happy to review fixes in PRs if you're already...
I'd be happy to add a copy of `unicode_safe` to ckanext-scheming so it could be used on 2.7. I'm indifferent about 2.6 as that's not an officially supported release anymore
Would you provide the full traceback instead of just the last line? Are you using a release version or the current master release of scheming? Does the error appear in...
this won't work for resource fields, group/org fields or fields that are part of the original package schema. I think this feature would be better implemented in ckan core package_update...