Password policy error on install

Just installed a copy of drupal commons on one of my websites to take a look at the admin functionality, and it looks like the password policy module is not working.  At the end of the install I received an error about the policy table not existing, and when I logged in and took a look around at the logs I found this error:

Column length too big for column &#039;policy&#039; (max = 255); use BLOB or TEXT instead query: CREATE TABLE password_policy ( `pid` INT NOT NULL auto_increment, `name` VARCHAR(64) NOT NULL DEFAULT &#039;&#039;, `description` VARCHAR(255) DEFAULT &#039;&#039;, `enabled` TINYINT NOT NULL DEFAULT 0, `policy` VARCHAR(1024) NOT NULL DEFAULT &#039;&#039;, `created` INT NOT NULL DEFAULT 0, `expiration` INT DEFAULT NULL, `warning` VARCHAR(64) DEFAULT NULL, `weight` TINYINT NOT NULL DEFAULT 0, PRIMARY KEY (pid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in <path to website>/includes/database.inc on line 550.

Not sure if this is something wrong on my web server or with drupal commons.  Thanks!

Comments

mike.stefanello

Hi, That looks to be

Hi,

That looks to be server-specific. I can safely save I've installed Commons a few hundred times on a variety of different hardware setups and have never experienced this. I would recommend contacting your hosting provider with this error and see if that clears anything up. Do you know what version of MySQL you're running? Have you ever encountered any similar problems with Drupal using this host? I'd also check the issues page on Drupal.org for the Password Policy module.

Mike

jedibfa

Thanks for the info.  Yeah, I

Thanks for the info.  Yeah, I meant to take a look at the mysql version over the weekend (I posted this as I was running out the door, so I missed a step), and it turns out the webhost is running an older mysql build: 4.1.20.  I'll try setting this up on a newer box and see if I get a clean install.

Thanks again!

mike.stefanello

Well that's good to know. Try

Well that's good to know. Try to get MySQL 5+. That should clear everything up.

jedibfa

That did it...

Switched to another server for testing (which has MySql 5.1) and no more DB errors. Thanks for the help!

mike.stefanello

You're welcome!

You're welcome!

jay

This is a good example..

.. of the reason we'll want to incorporate into Commons that new functionality we're creating around issues / answers / ..., eh, Mike?  :-)

mike.stefanello

Ah, very true. Good use case

Ah, very true. Good use case here. I could load up our q&a dev component, but it might make others jealous that they don't have it yet. What do you think? No better site to try it out on. Might be a good idea - we could pin a lot of 'best answers' on most of these discussions.