From a42be6e1d6989eff8e658b8e4cecf0c1fdcc14c4 Mon Sep 17 00:00:00 2001 From: Christopher Tull Date: Thu, 25 Oct 2018 13:45:23 -0700 Subject: [PATCH] Clarify that a commit is needed after login_user Previously one needed to look at the API documentation for `login_user` to know that a commit was necessary to get tracking to work. This adds a small note to the entry for `SECURITY_TRACKABLE` indicating that a commit is needed. --- docs/configuration.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/configuration.rst b/docs/configuration.rst index b696586d..c2dff6c2 100644 --- a/docs/configuration.rst +++ b/docs/configuration.rst @@ -190,9 +190,10 @@ Feature Flags option. Defaults to ``False``. ``SECURITY_TRACKABLE`` Specifies if Flask-Security should track basic user login statistics. If set to ``True``, ensure your - models have the required fields/attributes. Be sure to - use `ProxyFix `_ if you are using a proxy. Defaults to - ``False`` + models have the required fields/attributes + and make sure to commit changes after calling + ``login_user``. Be sure to use `ProxyFix `_ if you are using a proxy. + Defaults to ``False`` ``SECURITY_PASSWORDLESS`` Specifies if Flask-Security should enable the passwordless login feature. If set to ``True``, users are not required to enter a password to login but are