Act on all entites, not just translatable entities

Created on 31 August 2022, about 2 years ago
Updated 20 June 2024, 5 months ago

Problem/Motivation

Not all content types are translatable. This module _could_ deal with these too.

Steps to reproduce

Typical use case:
1. Primary site content is only in one language (including landing pages, homepage, etc.). These node types are not translatable.
2. Only one content type is translated. Let's call it "widgets".
3. I view a widget that is translated.
4. I click a link in the site-wide navigation.

Best case scenario:
I end up at a URL like /fr/node/31 because Drupal doesn't know how to give this a URL alias.

Worst case scenario:
I get a fatal error about "InvalidArgumentException: Invalid translation language" because some bit of code doesn't have anything as complicated as \Drupal\content_translation_redirect\EventSubscriber\RequestSubscriber::checkContentEntityCanonicalRoute()

Proposed resolution

Act on all entity types.

Feature request
Status

Closed: duplicate

Version

1.0

Component

Code

Created by

🇨🇦Canada dalin Guelph, 🇨🇦, 🌍

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024