Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.2.2
-
-
Empty show more show less
-
Yes
-
Maintenance 27, Maintenance 28, Maintenance 29, Maintenance 30
-
5
Description
Situation:
- In JCR is linked by path, but field expects by id
- Or vice versa: In JCR is linked by id, but field expects by path
- This can happen when changing the field's config, but still have old content. Migrations, try outs, artefact data etc
Problem:
- In both cases one can not open the dialog at all! => the author can not change it
- In the past one just saw the plain property value.
- In JCR is linked by path, but field expects by id
Caused by: javax.jcr.RepositoryException: Not an absolute path: 5c2c69ec-925f-4aca-9321-a143a4b9b1d2
- In JCR is linked by id, but field expects by path
Caused by: java.lang.IllegalArgumentException: /travel/tour-type at org.apache.jackrabbit.core.id.NodeId.<init>(NodeId.java:128) ~[jackrabbit-core-2.20.0.jar:2.20.0]
Solution:
About path vice versa:
- If the stored value can not be resolved, let the dialog open.
- Show the value as it is stored
About the linked node is deleted:
- The field shows empty! This is not good as the author doe snot see what the link was/where it linked to.
- The field should show then the stored value, and maybe communicate that the target node is not resolvable.
Checklists
Acceptance criteria
Attachments
Issue Links
- causes
-
MTE-123 Redirect template dialog should store node by ID
-
- Closed
-
- is cloned by
-
MGNLUI-6257 LinkFieldDefinitionConverter assumes default converter touuid
-
- Closed
-
-
MGNLDAM-905 Changing value to null in damLinkField causes NPE
-
- Closed
-
- is related to
-
MGNLUI-6774 DOC: Link field changed formats in 6.2.4
-
- Closed
-
- mentioned in
-
Page Loading...