[PAGES-909] URL Translation for FreeMarker and Delivery API Created: 25/Oct/22  Updated: 07/Feb/24  Resolved: 07/Feb/24

Status: Closed
Project: Magnolia pages module
Component/s: SPA Renderer
Affects Version/s: 6.2.24
Fix Version/s: None

Type: New Feature Priority: High
Reporter: Bartosz Staryga Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MURLTRANS-24 Add support for Delivery API In Progress
relates to MURLTRANS-5 Allow translation for any workspace Open
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: AuthorX improvements
Team: AuthorX

 Description   

Now we can use https://www.magnolia-cms.com/marketplace/detail/url-translation.html for FreeMarker.

This module is installed in the majority of FreeMarker-based projects.

Now that we push more towards headless, we keep getting questions about how to support URL translations in headless scenarios.

The module currently does not offer this feature.

Could we productise the module and improve it with Deliver API support?



 Comments   
Comment by Christopher Zimmermann [ 07/Nov/22 ]

Thanks bstaryga .. Can you add the usecases that you know of for headless? What featues are currently missing in headless mode? (It seemed like there were a few when we discussed over coffee.)

Comment by Bartosz Staryga [ 08/Nov/22 ]

czimmermann 
There is one use case .

We have the following page tree:

home
  |_ about-us

Home page is accessible via foo.com
About Us is accessible via foo.com/about-us 

Home page JSON via foo.com/.rest/delivery/pages/home
About Us JSON via foo.com/.rest/delivery/pages/home/about-us 

JavaScript determines which node it should fetch from the URL pathname - the about-us bit.

So now I want to have a page in polish. Without translation, the page would look like this:
foo.com/pl/about-us 
And this is all good. JS would fetch the correct node.

The problem we have is when like to have translated URL e.g.:
foo.com/pl/o-nas or foo.com/o-nas
JS would try to fetch a page
foo.com/.rest/delivery/pages/home/o-nas 

And this node does not exist

Comment by Pierre Sandrin [ 20/Jan/23 ]

Here a productive Magnolia DX-Core Headless usecase:

https://sihlcity.ch/en/freizeit-kino/

they wanted to have

https://sihlcity.ch/en/leisure-cinema/

but we had to tell them that the URLTranslationModule is not supported in headless projects.

Comment by Richard Gange [ 07/Feb/24 ]

Hey Everyone-

Let me close this issue since I've been using MURLTRANS-24 to track the progress. A POC is ready with a formal release to follow in the coming days.

BR
Rich

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