Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
6.2.5
-
None
-
None
-
Empty show more show less
-
Yes
-
Yes
-
Nucleus 36, Nucleus 41
-
2
-
Yes
Description
Steps to reproduce
- Â Create a switchable field in a custom app detail form containing complex fields (use attached module, navigation-app the creation element form)
- Â Open the form, select one of the options and save a value
- Check in JCR browser the stored value under /baseNavigationLinkSite
- Edit the created element by selecting another option, enter a new value and save.
- Check in JCR browser the new value
Â
Expected results
Previous value should have been overwritten by the new value
Actual results
Both values are kept
Workaround
Select field property actually points to the last stored option which would serve to discard values that haven't been chosen.
Development notes
Despite using currentItemProvider as indicated in docs, values for each option are kept
Checklists
Attachments
Issue Links
- duplicates
-
MGNLUI-5327 Switchable field won't remove a previously persisted property when saving the second time around
-
- Closed
-
-
MGNLUI-7030 Switchable field creates empty contentNodes for non selected option
-
- Closed
-
- is duplicated by
-
MGNLUI-5550 New SwitchableField stores values of unselected fields
-
- Closed
-
-
MGNLUI-8165 Non-selected values are kept in switchable field
-
- Closed
-
- is related to
-
MGNLUI-8070 Boolean properties persisted by previously selected form in switchable field are not removed from JCR
-
- Open
-
- is causing
-
MX-193 Loading...
1.
|
Implementation |
|
Completed | AntonĂn Juran |
2.
|
Code review |
|
Completed | Adam Siska |
3.
|
Pre-integration QA |
|
Completed | Adam Siska |
4.
|
Final QA |
|
Completed | Adam Siska |
5.
|
Docu |
|
Closed | Adrian Brooks |