I'am experience some problems when creating a node which content type has Multilingual support disabled. The node doesn't show up in the content list or in the view it is supposed to be listed in. The node stores properly in the database so it is actually created. After some researches I noticed that the node will show up in the content list and in my view if i enable "Enabled, with field translation" on my content type.
This problem occurred when I updated to the latest dev version(7.x-1.0-beta2+9-dev) from 7.x-1.0-alpha2.

Comments

Erik.Johansson’s picture

Erik.Johansson CreditAttribution: Erik.Johansson commented
Title: Nodes that don't have multilingual support enabled won't show up in content list on node creation. » Nodes that doesn't have multilingual support enabled won't show up in content list on node creation.
plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented

Possibly related: #1890346: Entity language change not handled on non-translatable entities with translatable fields.

Erik.Johansson’s picture

Erik.Johansson CreditAttribution: Erik.Johansson commented

The patch et-disabled_translation-1890346-2.patch did not fix my problem. Nodes won't show until i've enabled multilingual support on the content type.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Status: Active » Postponed (maintainer needs more info)

After reading the OP again: since ET doesn't implement listing filters I think this might be caused by the Multilingual content module belonging to the i18n project. Is it installed? And if so does disabling it fix the issue as well?