-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Selecting "Create" or "Edit" results in "Internal Error{" due to "AttributeError: 'tuple' object has no attribute 'items'" #2546
Comments
..and the issue appears to be related to WTForms.. in prod we're running 3.1.2.. and latest is 3.2.1 and generates this issue. As such, I'll close this off here.. and raise at: https://github.com/pallets-eco/wtforms |
Reopening as per the following comment on the WTForms issue (pallets-eco/wtforms#864 (comment))
|
I have encountered the same issue today; it happens with WTForms 3.2.0 and 3.2.1. My temporary solution is to pin WTForms to 3.1.2. |
The underlying issue here was fixed recently in this PR: #2341 It's currently available as Flask-Admin v2.0.0a. Please note this is a pre-release version of v2, so it is not guaranteed to be stable. I've been using it successfully and without issue for a while now though. I would suggest trying it out, but be careful before using it in production. Also consider following #2451 to track when v2.0.0 officially releases. I will close this for now as I believe the issue in code is fixed - it is a matter of getting a v2.0.0 release published. |
I've hit an issue with a couple of my Flask-Admin applications, and can recreate in the attached example.
The issue is that when clicking "Create" or "Edit" Flask-Admin errors with the below traceback:
Now, I do apologise if this is the wrong place to start to ask about this issue. But, from the above, you can see it's erroring from the builtin items. So, looking for guidance as to how to proceed.
To recreate:
Environment:
We have flask-admin 1.6.0 running in prod, without issue. But attempts to run the same known-good versions locally hit the same issue.. and locally this is across different macOS hosts.. and also attempted locally in docker and kubernetes with differing Ubuntu releases too.
The text was updated successfully, but these errors were encountered: