Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 3.3.2
-
Fix Version/s: 3.3.3
-
Component/s: None
-
Labels:None
Description
When logging is inactive (cannot choose between yes/no) because the user defined in CIVICRM_UF_DSN does not have SUPER privilege, we were not able to delete new custom fields. Database errors reported were either related to triggers or unable to delete a non-existent column.
To reproduce w/fresh 3.3.2 install:
1. The user defined in CIVICRM_UF_DSN does not have SUPER privilege.
2. Verify logging in Settings -> Misc is inactive (disabled) and set to no.
3. Create a new custom group and field.
4. Try to delete that custom field.
Sorry, but we are not able to troubleshoot any further or provide a patch at the moment. The fix was to grant the user defined in CIVICRM_UF_DSN SUPER privileges. There seems to be a code distinction between a "No" setting in Logging vs. a disabled, forced "No" setting.