Bug #2311
ux_felogin_pi1: Send mail with password
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Marcus Krause | % Done: | 100% |
|
| Category: | XCLASSes | Spent time: | - | |
| Target version: | 0.2.1 | |||
| Votes: | 0 |
Description
Bug in function "showForgot()":
In line 154 an email with the new password is send to $row['email'], but in line 115 only the columns "uid", "username" and "password" are read form the database.
Associated revisions
Bug #2311: ux_felogin_pi1: Send mail with password
Bug #2311: ux_felogin_pi1: Send mail with password
[Bug 2311] Move most of countRecords from the testing framework to oelib_db (tableHasColumn, tableHasColumnUid), r=saskia
[Bug 2311] Move most db-related functions from the testing framework to oelib_db (part 2), r=saskia
[Bug 2311] Move most db-related functions from the testing framework to oelib_db (shuffle some functions around), r=saskia
[Bug 2311] Move most db-related functions from the testing framework to oelib_db (add a function getColumns), r=saskia
[Bug 2311] use getColumnsInTable in the oelib configcheck, r=saskia
[Bug 2311] tableHasColumn should return false on an empty column name,
not throw an exception, r=saskia
[Bug 2311] Use the table/columns functions in realty, r=saskia
[Bug 2311] Move most db-related functions (count, hasRecord ...) from the testing framework to oelib_db, r=bernd
[Bug 2311] implement existsRecord, r=bernd
[Bug 2311] Implement existsExactlyOneRecord and existsRecordWithUid, r=bernd
[Bug 2311] Add $additionalWhereClause to db::existsRecordWithUid, r=bernd
History
Updated by Marcus Krause over 4 years ago
- Status changed from New to Accepted
- Assignee set to Marcus Krause
- Target version set to 0.2.1
Updated by Marcus Krause over 4 years ago
- Category set to XCLASSes
- Status changed from Accepted to Resolved
committed to branch RB-TER-DEV with changeset r14915
Updated by Marcus Krause over 4 years ago
- % Done changed from 0 to 100
Updated by Marcus Krause over 4 years ago
- Status changed from Resolved to Closed
Issue resolved with extension version 0.2.1