Martin Mahner
Martin Mahner
This happened to us out of the blue with copy/pasting a field into a form, where a field with the same `name` already existed. There's no way for an editor...
Uh nice. Would you try adding test models for these use cases?
This has been fixed in fb2bf46a01c4fb814d135956cbc1d6146b2272fb. I figured, you don't need to have specific field types for a Filter Input field.
I forked the project and named it [django-hashers-passlib-revived](https://pypi.org/project/django-hashers-passlib-revived/). It has support for up to Python 3.12 and Django 5.0.
I forked the project and named it [django-hashers-passlib-revived](https://pypi.org/project/django-hashers-passlib-revived/). It has support for up to Python 3.12 and Django 5.0.
Same here, the current version on Pypi does not support Django 4.x.
I forked the project and named it [django-hashers-passlib-revived](https://pypi.org/project/django-hashers-passlib-revived/). It has support for up to Python 3.12 and Django 5.0.
Closing this due to staleness.
The actual error here might be in kip, that it can't handle gracefully that the private key is not valid for the kip db.
"Secret key not valid". Try to delete your key files.