Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The schema module is reporting a table for which the schema and database are different under jwplayer_preset:
column machine_name - differences on: not null, default
declared: array('description' => 'TODO: please describe this field!', 'type' => 'varchar', 'length' => 255)
actual: array('description' => 'Unique machine name for every configuration preset.', 'type' => 'varchar', 'length' => '255', 'not null' => TRUE, 'default' => '')
Comments
Comment #1
deanflory CreditAttribution: deanflory as a volunteer commentedAny progress on this?
Comment #2
ron_s CreditAttribution: ron_s commentedCan you confirm if this committed patch resolves the issue?
https://www.drupal.org/node/2713921
Comment #3
BerdirNot sure where that default would come from, but this should indeed by resolved with the recent update.
Comment #4
deanflory CreditAttribution: deanflory as a volunteer commentedI've found that updating using the latest 7.x-2.x-dev (2016-May-04) with the following patches no longer reported a schema mismatch:
Thanks!