FlaskWTFDeprecationWarning with Flask_Security

python flask flask-security
user6723321 picture user6723321 · Sep 30, 2016 · Viewed 7.1k times · Source

I am received a warning every time I use Flask Security.

FlaskWTFDeprecationWarning: "flask_wtf.Form" has been renamed to "FlaskForm" 
and will be removed in 1.0.

Is this an issue with Flask Security or something I could address myself? I am using Flask-Security==1.7.5

from flask_security import current_user, login_required, RoleMixin, Security, \
SQLAlchemyUserDatastore, UserMixin, utils

I don't seem to import Flask_WTF directly.

Answer

Billal Begueradj picture Billal Begueradj · Sep 12, 2017

My answer is not inherent to your exact situation. However, the same warning message occurs when we code this:

from flask_wtf import Form

To fix this problem, you should use FlaskForm in place of Form:

from flask_wtf import FlaskForm

This is highlighted on GitHub and I just want to share the solution here to help any eventual doer who might face it in the future.

Related questions

How do you implement token authentication in Flask?

I'm trying to allow users to login to my Flask app using their accounts from a separate web service. I can contact the api of this web service and receive a security token. How do I use this token to …

Read More
How to get current user when implementing Python Flask-Security?

I am using Flask-Security to set up user authentication for my app but I am struggling with getting the email address or ID of the currently logged in user so I can query a table with that particular users details. …

Read More
Testing Flask login and authentication?

I'm developing a Flask application and using Flask-security for user authentication (which in turn uses Flask-login underneath). I have a route which requires authentication, /user. I'm trying to write a unit test which tests that, for an authenticated user, this …

Read More