Closed (fixed)
Project:
Password Policy
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Apr 2007 at 21:14 UTC
Updated:
31 Jul 2008 at 04:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
jonathan_hunt commentedTo migrate this module to 5.x, I've made the following changes:
svn diff below.
Files attached.
It would be good to see this module integrated with the password strength indicator for D6. http://drupal.org/node/143026
Comment #2
manocha_ak commentedhey i dould not see the svn difference or the file attached for porting timeline module to Drupal 5.x
Comment #3
Christefano-oldaccount commentedHere is a patch against HEAD that uses jonathan_hunt's code. I haven't tested it yet.
Comment #4
Christefano-oldaccount commentedRight, the patch.
Comment #5
seanrThis is still a bit buggy. Once you create a profile, the list of profiles doesn't display correctly.
Comment #6
seanrComment #7
seanrHere's an updated patch which fixes the issues I've found so far with the 5x port and adds password expiration from http://drupal.org/node/150079
Comment #8
Varyag commentedHi All
seanr, I`ve patch the password_policy HEAD version with your patch.
After install module I try configure password policy module. And I ahve next errors
in the tab "list"
user warning: Unknown column 'created' in 'field list' query: SELECT id, name, enabled, description, created FROM password_policy ORDER BY name in *** \www\includes\database.mysql.inc on line 172.
and error in tab "expired accounts" :
user warning: Table 'drupal5.password_policy_expiration' doesn't exist query: SELECT COUNT(*) FROM password_policy_expiration p INNER JOIN users u ON p.uid = u.uid WHERE p.blocked > 0 in *** \www\includes\database.mysql.inc on line 172.
user warning: Table 'drupal5.password_policy_expiration' doesn't exist query: SELECT p.*, u.name FROM password_policy_expiration p INNER JOIN users u ON p.uid = u.uid WHERE p.blocked > 0 ORDER BY blocked DESC LIMIT 0, 20 in *** \www\includes\database.mysql.inc on line 172.
Comment #9
deekayen commentedIt's unfortunate that 5.x got skipped, but I need to implement password expiration and it'll be a couple months before I'm on 6.x.
I'm attaching improvements to #7 which address #8, as well as coder module notices (which found some bugs like user_mail()). It also moves what was in #7 pointing to admin/settings/password_policy to admin/user/password_policy so the former hook_settings() can be in the admin/settings/password_policy slot.
Since I'm probably not the only one stuck on 5.x for a while, I propose 5.x still get its own branch. That probably mean making a momentary 5.x commit to HEAD, branching, and then re-committing the 6.x code to refresh its newness.
I have coded, installed, run simpletest, and gone through the forms, but haven't actually tested passwords and logging in and out or compared it to what has been done in 6.x, so I'm marking this "needs work" symbolically, but I would like it to be committed anyway. The diff is against a 1/4/2007 20:00 checkout of HEAD. I think it's probably at least worthy of getting its own commit so this 5.x upgrade patch doesn't get any bigger, and address http://drupal.org/node/150079, http://drupal.org/node/266429, and work out the details of a 5.x to 6.x upgrade later.
Comment #10
miglius commentedThanks. I will install it, test several usecases and if everything goes well, will create a branch for it.
Comment #11
miglius commentedI have created a D5 release based off your patch.
Comment #12
shariharan commented@miglius : When are you planning to release the 5.x version ?
Comment #13
miglius commentedA dev release was released but not explicitly listed to be shown. It is now.
Comment #14
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.