@hgy Thanks for that! We actually ended up needing to go a completely different route for this, abandoned the routes files.. it actually worked out very nicely, your use of settings is one of the pieces of our solution too for the grouping and control of the base path. Good old translatable settings hahaha. We also built a Trait, which we add to any controllers we want to get customized slugs from, it exposes a function we call from the language switcher to pull alternative locales.
I also wanted to share this language switcher file, which works pretty well with custom slugs on a default build using the Blog and Pages modules. This is likely not the best way to do it, but it's a good starting point. Hope this helps someone else!
@php
// Initialize optional variables
$post = empty($post) ? null: $post;
$page = empty($page) ? null: $page;
$links = array();
foreach (LaravelLocalization::getSupportedLocales() as $locale => $language) {
if ($post) {
$url = LaravelLocalization::getLocalizedURL($locale, $post->translate($locale)->slug);
}
elseif ($page) {
$url = LaravelLocalization::getLocalizedURL($locale, $page->translate($locale)->slug);
}
else {
$url = LaravelLocalization::getLocalizedURL($locale);
}
$links[$locale] = array(
'url' => $url,
'language' => $language
);
}
@endphp
@foreach ($links as $link)
<a href="{{ $link['url'] }}">{{ $link['language']['name'] }}</a> |
@endforeach
