The schema module is reporting a table for which the schema and database are different under password_policy in numerous places with lots of unexpected columns:
column name - difference on: length
declared: array('description' => 'TODO: please describe this field!', 'type' => 'varchar', 'length' => '255', 'not null' => TRUE, 'default' => '')
actual: array('description' => 'The name of the policy.', 'type' => 'varchar', 'length' => '64', 'not null' => TRUE, 'default' => '')
config: not in database
pid: unexpected column in database
description: unexpected column in database
enabled: unexpected column in database
policy: unexpected column in database
created: unexpected column in database
expiration: unexpected column in database
warning: unexpected column in database
weight: unexpected column in database
primary key:
declared: array('name')
actual: array('pid')
unique keys name: unexpected (not an error)
Comments
Comment #1
AohRveTPV CreditAttribution: AohRveTPV commented"Needs work" is only when there is a patch. See https://www.drupal.org/node/156119.
Thanks for reporting the bug.
Comment #2
AohRveTPV CreditAttribution: AohRveTPV commentedI think this may be due to #2027019: Upgrade from 7.x-1.x to 7.x-2.x not possible. Upgrading from 7.x-1.x to 7.x-2.x is broken at present. To use 7.x-2.x, 7.x-1.x should first be uninstalled.
Did you previously use 7.x-1.x on the site on which you are getting these mismatch indications?
Comment #3
AohRveTPV CreditAttribution: AohRveTPV commentedComment #4
deanflory CreditAttribution: deanflory commentedI believe I have had Privacy Policy installed since 1.x and did not uninstall before updating to 2.x.
Disabling, uninstalling and re-enabling the Password Policy module did indeed fix the schema issue.
Schema now matches for:
Thanks for your time.
Comment #5
deanflory CreditAttribution: deanflory commentedComment #6
deanflory CreditAttribution: deanflory commented