Error checking in this module is lacking
Chris Johnson - December 3, 2006 - 18:28
| Project: | Password policy |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dayre |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
From admin->password policy, I am able to select "add" to create a new policy. I can fill in the fields. I click "Save" and it tells me it saved it but it doesn't appear in the list.
In fact, the tables don't even exist because the install didn't make sure they did, and the save doesn't check for success.
#1
It would be helpful to know what Drupal version you were using with this module and what database system. I haven't gotten around to creating a branch for this to mark it as 4.7 or 5.0. It has only been tested with 4.7.3 and 4.7.4 and only works with MySQL.
You mentioned that the install failed and the tables did not get created. If the tables didn't get created, it would have been due to a SQL error. If there were no tables created, then the save would also cause a SQL error. Drupal catches SQL errors and displays them on the next page rendering.
Were there any errors displayed ? If so, what were they ?