It really seems that there is confusion between code and database...
The code accesses the database, and performs actions based on what it finds or doesn't find... If the code doesn't look in specific/particular locations (ie a plugns software has been removed) then the information that remains in the database will not cause the code to "make a decision" about what to do next. Such leftover data will merely take up space, and in some queries will take up time to be pulled into a variable.
So, if the "offending" code (which none of the plugins listed when installed correctly to a correctly built store should have any true/direct effect on the use of the password or the action that should occur after providing a new password) is removed/replaced with original code then the extra database "bits" will have no effect on the functional results, but if the code remains, then even if the applicable database bits are removed, the code may actually recreate aspects of it to "protect itself and the store".
Portions of the password system are shared for customer and admin in more recent versions, if not woven correctly, an action may go awry...
Forgot the important part of this ppost: so what was restored? Database or files? If database, then have lost all transactions from the time of the backup and now. If files, weel there is something different between the old fileset and what was replaced. Hopefully a comparison can still be made if a backup was collected before restoration. If both were replaced, well may never know, but doubt it is a database issue. If you need to force an expired password, that can be arranged.



Reply With Quote
