Viewing 1 replies (of 1 total)
  • VERSION 3.4.8

    This error appears to be caused by either
    a) resetting the users password to a password that is not considered as strong. The user password can be changed in the admin panel to a weak password after account creation, but it cannot be made weak during user registration.

    or

    b) Erroneous data being written into the user meta database table

    or

    c) using the password reset feature

    QUICK FIXES TO TRY:
    1) If there is a user who still has access, go to the administration panel and reset the password to a strong password (8 characters, a capitial, a number, and a symbol)

    2) Go to the database and in the users meta table, set the value of [dbprefix]_capabilities for the user to: a:1:{s:13:"administrator";s:1:"1";}

    3)restore a database backup from a time prior to the problem occurring, if that is an option

    OTHER INFORMATION FOR THE DEVELOPER:
    1) The password reset feature does not work properly, at least it doesn’t if you are using the login rewrite feature

    2) You probably should not be able on the user panel to reset a user password to a weak password as this will also cause the behavior

    Good Luck

Viewing 1 replies (of 1 total)
  • The topic ‘Notice: unserialize() – Please patch!’ is closed to new replies.