[MURLTRANS-23] editing copied or duplicated page redirects to source page Created: 04/Mar/22  Updated: 08/Feb/24

Status: Selected
Project: URL Translation
Component/s: None
Affects Version/s: 6.2.3
Fix Version/s: 6.2.5

Type: Bug Priority: Critical
Reporter: Martin Schmid Assignee: Unassigned
Resolution: Unresolved Votes: 5
Labels: i18n, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.2.16


Issue Links:
Relates
relates to MURLTRANS-22 Add validation to locale values Selected
relation
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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Visible to:
Andre Zschaebitz, Lukas Jakobitz
Work Started:

 Description   

Steps to reproduce

  1. create multilang environment
  2. create page + lang variants
  3. add translated page names
  4. copy + paste page OR duplicate page
  5. try to open page for editing

Expected results

new page will become open for editing. 

Actual results

page editing opens source page for editing. 

the content operator may not notice this and override the origin content.  

Workaround

remove translated page name in JCR >> need admin role

Development notes

actually this behavior may be the cause for MURLTRANs-22, because when copying or duplication a page both versions have the same translated page name. 



 Comments   
Comment by Antony Hutchison [ 11/Oct/22 ]

Does this imply that duplicate names are possible? For example, we could create a page named 'a', create a page 'b' and translate the name to 'a', and so on with page 'c', page 'd'... exactly the same as duplicating / copy-paste of a page.

Logically, if there's a natural page named 'a' then that should show, but then it could possibly switch to the wrong language.

Whilst the remedy for the edit-mode seems apparent to me (don't apply the filter on author in edit-mode, which should be available from the magnolia context), how to gracefully handle this with published content needs careful consideration.

Generated at Mon Feb 12 11:08:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.