Opened 10 years ago
Closed 9 years ago
#576 closed improvement (fixed)
Template: Cleanup orphaned preset options
Reported by: | prcua | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 7.4.1 |
Component: | Core | Version: | 7.2.1 |
Keywords: | Cc: |
Description
For an attribute defined as a string with a preset input mode, if I populate options and later rename the attribute, the existing options are lost. If I change the attribute name back to the original name, the attribute options reappear. This lead me to believe that the original options are orphaned in the database. Existing Attribute options should apply to the renamed attribute.
Change History (2)
comment:1 Changed 10 years ago by car031
- Milestone 7.3 deleted
- Type changed from Bug to Improvement
comment:2 Changed 9 years ago by car031
- Milestone set to 7.4.1
- Resolution set to fixed
- Status changed from new to closed
- Summary changed from Template: Renaming Attribute Yields Loss of Existing Attribute Options to Template: Cleanup orphaned preset options
Note: See
TracTickets for help on using
tickets.
When you change the name you lose the options, now we take care of really deleting all the options once you save the template after the rename so the database is always clean