Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 1.2
-
Fix Version/s: 1.2
-
Component/s: None
-
Labels:None
Description
In the script that upgrades the MySQL database from 1.1 to 1.2, there's a line that adds the options_per_line field to the civicrm_custom_field table:
ALTER TABLE civicrm_custom_field ADD options_per_line int unsigned DEFAULT 1 COMMENT 'number of options per line for checkbox and radio';
Here, the default for the field is set to "1." This is fine for custom fields that are checkboxes or radio buttons. However, for date and text custom fields, if options_per_line is set to "1," the text or date fields are not shown when editing custom field data in CiviCRM, or when conducting advanced searches.
Changing options_per_line back to "0" for text and date fields fixes the problem.
I'm not sure how select fields are affected by options_per_line being set to "1," so you might want to check on that as well.