Wrong url - Translation in Fallback Type: free

[zkrechowiec]

Bug Report

Current Behavior I have a site with multiple languages (EN as default, FR as secondary), when I translate a news item, the slug for my news item contains the path_segment EN ex: EN: /newspress/detail-view/test-en FR: /fr/actualites/vue-detaillee/test-en instead of /fr/actualites/vue-detaillee/test-fr

If I don't configure a fallback language (which is what I need on my site), I can't access the detailed view of my FR news (by going through the language menu from the EN detailed view or the FR list view) I get a 404.

If I add a fallback to the EN language still in free mode, then the detailed view works with the url /fr/actualites/vue-detaillee/test-en

My url rewriting is configured like this: routeEnhancers: News: type: Extbase limitToPages:

• 91 extension: News plugin: Pi1 routes:

• routePath: '/{news-title}'
  _controller: 'News::detail'
  _arguments:
    news-title: news

  defaultController: 'News::list' defaults: page: '0' aspects: news-title: type: PersistedAliasMapper tableName: tx_news_domain_model_news routeFieldName: path_segment

And my language menu is generated by the LanguageMenuProcessor

Thanks in advance, Zoïa

Environment

• TYPO3 version(s): 12.4.20
• news version: 11.4.2
• Is your TYPO3 installation set up with Composer (Composer Mode): yes

[ulrike-cosmoblonde]

Hi, I can confirm this behaviour. In freemode, the generated URLs to news detail pages are always using the original path segment and never the translated path segment. This leads to a 404 (unless a fallback language is configured). It would be better to get the correct language-aware URLs.

[georgringer]

I am not sure if this is really a news issue but a core issue?

[ulrike-cosmoblonde]

@georgringer I agree! It is a core behaviour concerning any data type and currently the only workaround I could find is to configure a fallback language even though the language mode is "free" and not "fallback"