Opened 11 years ago
Closed 10 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 by , 11 years ago
| Milestone: | 7.3 |
|---|---|
| Type: | Bug → Improvement |
comment:2 by , 10 years ago
| Milestone: | → 7.4.1 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
| Summary: | Template: Renaming Attribute Yields Loss of Existing Attribute Options → 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