Translated content doesn't get aliased path in views path

olafgrabienski commented 3 weeks ago

Description of the bug

This is a follow-up to #6745 (about views Title fields with links). This one here is about views Path fields:

Paths to translated content which is listed in views, e.g. on the "Manage content" page, aren't rendered as the aliased path. Path aliases in views work only, if interface and content language are the same.

Steps To Reproduce

To reproduce the behavior:

Enable Content Translation, Language and Locale from Backdrop core.
Add a second language, i.e. German.
Configure the Page content type, go to the tab "Multilingual support", and choose "Enabled, with translation".
Create a page of title "Hello world", put some content in the body, set the language to English, and save the page. The page gets a URL like example.com/hello-world.
Hit the "Translate" tab, and add a translation. The translated page gets a URL like example.com/de/hallo-welt.
Switch the Backdrop interface back to English, using the language switcher in the Admin bar.
Go to the Manage content page, edit the view and add a Path field.
Back on the Manage content page, inspect the path of the pages created above.

Actual behavior

The path of the English page "Hello World" is the alias /hello-world (as expected). The path of the translation "Hallo Welt" isn't an alias but the node ID path, e.g. /node/7.

Expected behavior

The path of the translation "Hallo Welt" is an alias, e.g. /de/hallo-welt.

argiepiano commented 3 weeks ago

PR submitted.

The PR actually sends the language object to l() in order to get the aliased path when available. Before the PR, there was no attempt to get the aliased path, despite the description of the views field!