[MGNLUI-6735] NodeNameValidator doesn't work at root level Created: 26/Mar/21  Updated: 14/Jun/21  Resolved: 11/Jun/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.5
Fix Version/s: 6.2.10

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PAGES-447 Can't add child page with the same na... Closed
causality
relation
is related to MGNLUI-6455 nodeNameValidator doesn't work correc... Closed
supersession
is superseded by MGNLUI-6678 Creating a page with an identical nam... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Epic Link: UI framework implementation
Sprint: UI FW 30

 Description   

Steps to reproduce

  1.  Create page with name A under root
  2.  Create page with name A under root again

Expected results

Validation error is shown that a page with the same name already exists

Actual results

Nothing happens, there's no feedback for the user. No error/warning message is shown and nothing appears in logs

Development notes

This works ok in previous version of pages-app 6.2.4 (Magnolia 6.2.5)

NodeNameValidator is not triggered at root (valueContext.getSingle())



 Comments   
Comment by Roman Kovařík [ 14/Jun/21 ]

For release notes:

attempts to create of content (e.g. a page) with existing name now produce validation error at JCR root level as well (used to work only deeper level).

Generated at Mon Feb 12 09:39:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.