AnsweredAssumed Answered

enum field became varchar in conversion to 7.5

Question asked by Francesca Shiekh on Mar 17, 2015
Latest reply on Mar 17, 2015 by Francesca Shiekh
in v6.2 we created a new module called Address Locations, this originally had a text field for country which was later changed to enum.

Though the definition in 
still shows enum in v7 as it did in v6

  'address_country' =>
  array (
    'required' => false,
    'name' => 'address_country',
    'vname' => 'LBL_ADDRESS_COUNTRY',
    'type' => 'enum',
    'massupdate' => 1,
    'comments' => '',
    'help' => '',
    'importable' => 'true',
    'options' => 'wr_country_list_DD',
    'merge_filter' => 'enabled',

In v7 Studio sees this as a Text field (Studio in v6.5.18 sees it as an enum).

I checked the files in custom/Extensions/modules/addlo_Address_Locations/Ext/Vardefs/ and the resulting custom/modules/addlo_Address_Locations/Ext/ and there is nothing to suggest a reason for the difference in field type.

Any suggestions on where else to look for some mistaken redefinition?