[MGNLSITE-79] "Move Before" and "Move After" buttons' states are not handled correctly Created: 18/Oct/16  Updated: 30/May/17  Resolved: 30/May/17

Status: Closed
Project: Magnolia Site Module
Component/s: app
Affects Version/s: 1.1.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Sang Ngo Huu
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d 1h
Original Estimate: 3d

Attachments: PNG File reproductionImage.png    
Issue Links:
Relates
relates to MGNLUI-4207 Replace move-predicates back with dro... Closed
relates to PAGES-133 Update the TemplateTypeRestrictionDro... Closed
relation
is related to MGNLUI-4194 Generalize code for move-availability... Closed
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
Date of First Response:
Sprint: Saigon 96, Saigon 97
Story Points: 3

 Description   

This issue occurs in Site app and Security app.

Steps to reproduce:

  • Open Site app
  • Create a folder
  • Create a content node inside that folder
  • Select that content node, open Move dialog
  • Deselect that revealed content node
  • Move Before and Move After will be enabled
  • Click on any of those buttons
    => Expected: The content node is moved to first level.
    => Actual: It disappears! We can see it using JCR app.

Consider to disable "Move before" and "Move after" in this case like Pages app because this issue doesn't occur in Pages app.

Side note: The issue doesn't come from "move" dialog epic because it even occurs in 5.4.10 which doesn't have "move" dialog enhancements.



 Comments   
Comment by Mikaël Geljić [ 15/May/17 ]

Ideally, fix for root-availability in MGNLUI-4207 should cover that, so the goal here would be to verify. Root-path configured in content-connector should be used when there is no selection.

Extended node for site-definition might be in the way; let's first try to fix it without extends.

Comment by Oanh Thai Hoang [ 30/May/17 ]

Confirm when doing QA: After MGNLUI-4207 integrated, Move After and Before is disable on Site app

Generated at Mon Feb 12 07:12:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.