Repeatable: Always
Steps to repeat:
1. Create a node of a Content Type without translations enabled.
2. Enable translations for that Content Type under Administration > Configuration > Regional and language > Content language settings
3. Edit the previously created node.
4. Under the "Translations" tab, the following error appears:
Translations Entity Error
5. Add a new node of that Content Type with translations enabled and the error message does not appear.

Notice: Undefined property: Drupal\node\Plugin\Core\Entity\Node::$translation in translation_entity_overview() (line 99 of core/modules/translation_entity/translation_entity.pages.inc).

CommentFileSizeAuthor
translation_entity_undefined1.png41.7 KBcraychee
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

YesCT’s picture

YesCT CreditAttribution: YesCT commented
Issue tags: +D8MI, +SprintWeekend2013

this is an awesome find!
with precise steps to reproduce.

the screenshot helps, and also cutting and pasting the error text allows screenreaders to follow the issue as well as google. :)

YesCT’s picture

YesCT CreditAttribution: YesCT commented

this was also seen in #1899486-4: unify dropbutton use of translate/translations wording in links

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Component: translation_entity.module » content_translation.module
penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾Seville 💃, Andalusia 🇪🇸, UTC+2 🇪🇺
CreditAttribution: penyaskito commented

Cannot reproduce. Maybe this was already fixed?

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Issue summary: View changes
Status: Active » Closed (cannot reproduce)

I also have not seen this. Please reopen if reproduced.