[MAGNOLIA-3983] MultiValueSaveHandler does not remove nodeData when there are no values Created: 24/Feb/12 Updated: 03/Apr/12 Resolved: 24/Feb/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4.6 |
| Fix Version/s: | 4.4.7, 4.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Description |
|
Suppose you have a checkbox control foo with two options bar and baz selected and a saveHandler} of type info.magnolia.module.admininterface.MultiValueSaveHandler. This will create a node named foo with two properties bar and baz}. You remove bar and only baz remains. Now, trying to remove baz does not work - the property will stay there unless you remove it manually, i.e. via JCR browser. |