See the attached screenshot. I downloaded and installed 6.x-1.x-dev and tried to define a simple policy (Name: default, 365 days expiration, 14 days of notification). What I got is the Password Policy screen with 'no policies defined' and an unlabeled radio button.

Tried other policies too, always the same result, unless I *only* choose to define a title without an actual policy.

My Drupal version is 6.6

CommentFileSizeAuthor
Screenshot-Password policies.png17.08 KBAnonymous (not verified)

Comments

miglius’s picture

miglius commented

Can you check the database to make sure that a database tables has been created?

Anonymous’s picture

Anonymous (not verified) commented

There are three tables created, password_policy + _expiration and _history. Uninstalling the module is properly deleting the tables.

miglius’s picture

miglius commented

Cannot recreate. The creation and deletion of the policies work fine for me.

Anonymous’s picture

Anonymous (not verified) commented

Fine. So what do you suggest? Stop using password policy, because it works for you? Maybe you should tell me what you need in order to help you fixing the bug... Maybe I am able to help you.

miglius’s picture

miglius commented

Can you paste here the content of the password_policy table?

Anonymous’s picture

Anonymous (not verified) commented

Sure, here we go:

== Table structure for table password_policy

|------
|Field|Type|Null|Default
|------
|//**pid**//|int(11)|Yes|NULL
|name|varchar(64)|Yes|
|description|varchar(255)|Yes|
|enabled|tinyint(4)|Yes|0
|policy|text|Yes|NULL
|created|int(11)|Yes|0
|expiration|int(11)|Yes|NULL
|warning|varchar(64)|Yes|NULL


== Dumping data for table password_policy
|1|default| |0|a:0:{}|0|365|30
miglius’s picture

miglius commented
Status: Active » Fixed

The issue was with the particular policy name "default". This is fixed in the dev version.

Anonymous’s picture

Anonymous (not verified) commented

I can confirm this for my installation. Thanks a lot!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.