UUID in `to` field: Allow selecting target language

[trych]

Hi there!

Thanks a lot for the plugin.

I am trying to set it up by picking pages in the to field, which I noticed writes uuids into the retour.yml file, which is what I would expect.

However, if I have a from field like en/foo, that redirects me to the page page://bar, I always end up at the default language mydomain.com/de/bar instead of the expected mydomain.com/en/bar.

Is there a way to stay in the correct language layer when using uuid redirects?

Thanks!

[distantnative]

Hmm, this is a bit tricky. Because for Retour it's not immediately clear that your from path en/foo contains the language - or assumes to set a language context. So it doesn't handle that.

And then the link field just allows selecting a page as UUID without specifying another language as the current language. And thus in turn, default is the current language when executing the route (as no language context is set) and you end up at the default language.

Probably best way to tackle this would be allowing to choose a target language when selecting a page/UUID (either done customary by Retour or as a default optional behavior of the Kirby link field).

I cannot give you any timeline on this. I would like to find a solution, but cannot commit to this fully at the moment. For the meantime, I think going with an actual URL/path might be the workaround.

[trych]

Thanks a lot for the response!

Choosing a target language would still require me to create two entries for a two language setup. It would be nice if there would be an option to let the plugin figure out the current language from the url automatically and then let it redirect to that specific language.

That might even be a general Kirby issue. I know I had to jump some hoops in my current project to enforce the current language in some of my plugin methods. In some contexts, I needed to do something like

site()->visit('home', $lang);

to force Kirby to jump to the current language. Not sure if this topic is directly related, but I just noticed there are some areas where the automatic redirecting throws you back to the default language unexpectedly.

And yes, I am fully aware that you have more important things on your plate right now. :)

So, no rush from me, I will just work with paths for now and hope editor's don't start renaming pages wildly.