Locked attribute removed in 2.0.0-beta1 version?

[polantis]

Hello,

Why is this attribut removed? I am using it when some one has made a valid subscription but has made some suspicious activities on my website. I need two fields: enable and locked

Do i have to create a new islocked function in my user class?

If i look at the user entity, it is not really usable..:

public function isAccountNonLocked()
{
return true;
}


Thank you,

Regards,

Guillaume

[stof]

if your project need it, you can add this field in your own child entity (and overwrite the Symfony interface method isAccountNonLocked()).

The property was removed of the bundle because the bundle itself was not providing any feature based on it, and was enforcing a specific implementation of isAccountNonLocked(), which was not flexible enough for some users, and which required an unused DB field for others. So we went the simplication way: not providing any field for it by default, and letting projects needing it implement it the way the want.

[XWB]

See above.