Page accessible via translated slug and original slug

Example:
German Page (default language) has url: https://website.de/unternehmen/germanpage
English Page has url: https://website.de/en/company/englishpage
The English Page will still be accessible via: https://website.de/en/unternehmen/germanwebsite

Config:

'languages' => true,
'languages.detect' => true,

Default Language de.php:

return [
  'code' => 'de',
  'default' => true,
  'direction' => 'ltr',
  'locale' => 'de_DE',
  'name' => 'DE',
  'url' => '/',
  'locale'  => [
    LC_COLLATE,
    LC_MONETARY,
    LC_NUMERIC,
    LC_TIME,
    LC_MESSAGES,
    LC_CTYPE
  ]
];

Secondary Language en.php:

return [
  'code' => 'en',
  'default' => false,
  'direction' => 'ltr',
  'locale' => 'en_US',
  'name' => 'EN',
  'url' => '/en',
  'locale'  => [
    LC_COLLATE,
    LC_MONETARY ,
    LC_NUMERIC,
    LC_TIME,
    LC_MESSAGES,
    LC_CTYPE
  ]
]

I believe saw this Issue being discussed on github In a multi-language setting, a non-default page version can be accessed both with the default language slug and its own translated slug. ยท Issue #2257 ยท getkirby/kirby ยท GitHub, so i updated my 3.5 Kirby to 3.6.6, since im not able to update to 3.7 or 3.8 currently. Sadly im still running into this issue. Any suggestions?

The issue has been moved and is still open, see Redirect requests to default language URI in secondary languages to the custom secondary language slug ยท Issue #3550 ยท getkirby/kirby ยท GitHub

I wonder how critical this really is, because the duplicate URLs will not appear anywhere or accessed by anyone except by chance when manually entering an URL into the address bar.

1 Like

Yea its really not that big of a problem, since im also having a canonical tag on my site that points to the correct english url.

I was just wondering if this is a fixed problem in some other version, or if im doing something wrong.