[MGNLUI-8421] RichText link to pages are not updated at JCR when a page is moved Created: 04/Oct/23  Updated: 01/Feb/24

Status: Accepted
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.39
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: RichTextEditor
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
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:
Epic Link: FieldsMaintenance
Team: Nucleus

 Description   

Steps to reproduce

  1.  Go to demo
  2.  At Pages app, create a page named test
  3. Create another page named test2
  4. Open test2 page and create a TextAndImage component
  5. Within the text field, create a link (magnoliaLink) to test page
  6. Go to JCR and check that the text property, within the generated link includes path=/test
  7. Go back to Pages-app and move the test page within travel site
  8. Check that the link still works (the link shown within the Preview option is correct)
  9. Go to JCR and check that the path within the text attribute hasn't been updated and still points to {{path=/test}

Expected results

The path is updated

Actual results

The path remains as when created

Workaround

N/A

Development notes

Under no headless approach, it doesn't matter. For solving the reference we just need the uuid and the workspace correctly set. You can even set a path property which does not exists and it will still be properly resolved.

The issue is under the SPA approach. The path returned is the old one (before the page was moved) and the links generated by the SPA approach are broken, as far as the page is not on that location anymore



 Comments   
Comment by Roman Kovařík [ 13/Dec/23 ]

Looks like everything works as expected. The UUID is there as well to always get the correct link.

The system doesn't start updating content in possibly thousands of nodes just because one page was moved due to performance reasons.

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