[PAGES-969] Prefix the paths in events sent by external pages widget Created: 09/Dec/22  Updated: 16/Feb/23  Resolved: 12/Jan/23

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Improvement Priority: Neutral
Reporter: Lam Nguyen Bao Assignee: Lam Nguyen Bao
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 3.5d Time Spent: 3.5d
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by PAGES-948 [Norsu] @path value in routeTemplate ... Closed
is caused by PAGES-942 [Norsu] Remove workspace from templat... Closed
dependency
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-988 QA Sub-task Closed Lam Nguyen Bao  
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)
Date of First Response:
Epic Link: TPR SaaS Norsu Pages
Sprint: AuthX 24 Xmas, AuthX 25
Story Points: 3
Team: AuthorX
Work Started:

 Description   

website is being used and show to url and other parts such as:

  • Iframe resource
  • Template definition
  • Selected element
  • Adding component

We need to omit/avoid showing of those root path value

 

UPDATE: After the workspace was removed in PAGES-942, the external page editor sends events with the "relative" path. Norsu Pages app needs to prefix the paths with workspace again.



 Comments   
Comment by Robert Šiška [ 19/Dec/22 ]

This is addressed in various tickets, which are currently merged on a feature/norsu-workspace-removal.

The iframe URL was addressed in PAGES-948. Template definition endpoint is not supported on norsu pages, but the template annotation endpoint was addressed in PAGES-942.

The element selection is still an issue, however.

Comment by Christopher Zimmermann [ 21/Dec/22 ]

I'm not sure if this is relevant. But please make sure that we do not hardcode "website" as a prefix. We will eventually support pageeditors in other apps with other "workspaces". (We have recently done work removing the hardcoding of "website" in other contexts. So it would be sad to "slip back" https://jira.magnolia-cms.com/browse/PAGES-457.) "website" is fine as a default.

If the above is necessary or introduces big hurdles, we could hardcode "website" for now - but then we need to improve that in the future. 

Generated at Mon Feb 12 06:23:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.