[MURLTRANS-7] Google Sitemaps App can not resolve URL-Translation paths for non default language Created: 17/Jun/19  Updated: 17/Jun/19  Resolved: 17/Jun/19

Status: Closed
Project: URL Translation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Thomas Peintner Assignee: Richard Gange
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to URLTRANS-6 Google Sitemap Module ignores name pr... 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:

 Description   

We are having a Magnolia 6.0.0 multisite installation with the URL-Translation Extension Version 5.6.2. 

For the URL-Translation Extension we use the standard field name and property type:
nodeType: mgnl:page
propertyName: name

The Google Sitemaps App is only creating entries with the default language, in our case German, but not resolving for example a second language like English.



 Comments   
Comment by Richard Gange [ 17/Jun/19 ]

Hello tpeintner-

Due to the fact Google Sitemaps module was deprecated I won't be fixing this issue. Please see https://documentation.magnolia-cms.com/display/DOCS57/Google+Sitemap+app. Thanks for reporting though. It was actually mentioned to me already in the community edition version (URLTRANS-6).

Cheers
Rich

Comment by Richard Gange [ 17/Jun/19 ]

Closing as "Won't fix" due to deprecation of the supporting module.

Comment by Richard Gange [ 17/Jun/19 ]

For more info please also see:

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