-
Notifications
You must be signed in to change notification settings - Fork 33
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
TypeError when editing ressources #90
Comments
What is your ckanext-scheming version? Older versions may cause this error. |
I'm encountering the same error even after a clean installation. I've attempted this with CKAN version 2.10.1 and Python versions 3.10, 3.8.13, and 3.9.18, and in all cases, I encountered the same error when attempting to upload a file. Unfortunately, I don't have any additional information to provide about the error at this time. Here's the content of my ckan.ini file:
I've double-checked the version of ckanext-scheming, and it appears to be up to date at version 3.0.0. Here is a list of the libraries installed in the environment:
and for information, here is the error mensage when i try to upload something:
Given this situation, I would greatly appreciate any assistance in resolving this issue. Thank you very much. |
The example schema references the |
I am Using Ckan 2.10.1 and just installed ckanext-validation. I have linked the required presets and the required presets
scheming.dataset_schemas = ckanext.validation.examples:ckan_default_schema.json scheming.presets = ckanext.scheming:presets.json Ckanext.validation:presets.json
Now when I click on an existing resource and even when I am not changing anything but clicking on "Update resource" I get this error:
TypeError: str cannot be used as validator because it is not a user-defined function
. Why is that and how can I fix this? I am quite new to the ckan world and it's also the first time working for me with ckanext-validation so maybe I am just missing something I don't know. Any help is much appreciated, thanks in advance!The text was updated successfully, but these errors were encountered: