Currently we allow to configure content language settings only for translatable entity types, but this is an unnecessary limitation, since language assignment settings apply also to language-aware but non-translatable entity types. Follow-up of.
Display all language-aware entity types on the content language settings page. Remove workarounds from aggregator.
User interface changes
When language module (and for this screenshot aggregator) is enabled:
When content translation is also enabled:
Beta phase evaluation
|Issue category||Bug because non-translatable types cannot be configured for language defaults on the common configuration screen. Even for their own one-off configuration screens need workaround to work see http://cgit.drupalcode.org/drupal/tree/core/modules/aggregator/src/FeedF....|
|Issue priority||Major because this affects all non-translatable language-aware entity types in core and contrib.|
|Prioritized changes||Prioritized because this reduces fragility by allowing to remove one-off workarounds and improves user experience by removing a confusing and unnecessary differentiation.|
|Disruption||No disruption foreseen.|