• "2599228 : Programmatically created translatable content type returns SQL error on content creation"

  • "https://www.drupal.org/files/issues/2019-01-23/2599228-128_.patch"
  • REASON: Translation Config Issues

• "2877994 : Path field deprecation and backwards compatibility for existing views"

  • "https://www.drupal.org/files/issues/2019-02-24/2877994-98.patch"
  • REASON: Paths cannot be developed in the

• https://www.drupal.org/project/token_filter/issues/3036541 - Token Filter schema is missing

  • This is needed to prevent Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for editor.editor.streamlined with the following errors: editor.editor.streamlined:settings.plugins.tokenbrowser missing schema errors when running Functional tests due to broken schema. Module needs to be reworked to use the ThirdPartySettings interface for Config Entities (*.third_party.module_name, getThirdPartySetting, setThirdPartySetting etc)

• https://www.drupal.org/project/drupal/issues/2952990 - Missing schema for display_options.defaults.sitename_title

  • This prevents schema validation error when a Feed is added with an Overridden Title field.

• https://www.drupal.org/project/drupal/issues/2599228 - Programmatically created translatable content type returns SQL error on content creation.
  • This prevents the packaging of translated content types (Article and Landing)
• https://www.drupal.org/project/drupal/issues/2770113 - Allow to skip translations import
  • When language is enabled and English is not the one and only language, the Drupal installer breaks trying to download the language because Interface Translation (locale) is not enabled. Workaround was to enable locale and deal with a host of other issues.
• https://www.drupal.org/project/drupal/issues/2666998 - Profile override config language.types.yml might not be imported correctly during installation
  • When Interface Translation (locale) is enabled, it handles Interface and Content negotiations the same. Workaround was to do it in code in install hook.
• https://www.drupal.org/project/drupal/issues/2845437 - Process translation config files for custom modules
  • Not an immediate issue, but if we want to translate our workflow states or anything else, this will bite us.
• https://www.drupal.org/project/drupal/issues/3023076 - Installing language programmatically will not install local translations
  • This is affecting our install profiles. Adding a language through code does not install our translations.
• https://www.drupal.org/project/drupal/issues/3006897 - Impossible to delete published translations on unpublished nodes
  • Not directly affecting us

• https://www.drupal.org/project/drupal/issues/2953331 - Sort of the moderated content queue page by state is broken (we have turned off the sort until this bug is fixed)
• https://www.drupal.org/project/drupal/issues/3021222 - Available states determined incorrectly for new content translations
  • When an English content item is published, its new translation will not be able to be saved as a draft. We will investigate to see if we can come up with a patch. Temporary workaround would be to adopt a modified (simpler) workflow which does not distinguish between editing/review of content before and after it has been published.
• https://www.drupal.org/project/drupal/issues/3029219 - State transition validation ignores language when determining "first time moderation" (see https://github.com/NCIOCPL/cgov-digital-platform/issues/475, which has a patch we might use until the core team addresses the problem)
• https://www.drupal.org/project/drupal/issues/2730631 - Node revision routes don't convert {node} param
  • The {node} parameter passed on an entity.node.revision route (such as http://www.devbox/node/88/revisions/200/view = entity.node.revision) is passed as a numeric NID, not as a processed Node object. Currently using manual type checking to workaround in docroot/profiles/custom/cgov_site/themes/custom/cgov/cgov_common/cgov_common.theme:cgov_common_theme_suggestions_page_alter()

• https://www.drupal.org/project/drupal/issues/784672 - Allow text field to enforce a specific text format
  • This is needed so that we can set the caption field to only allow simple html, and intro text to use our streamlined, etc.

• Views RSS display always outputs ‘submitted’ by and ‘authored on date’ inside the description tag

  • Despite not being in the RSS display at all, the RSS feed (Content format) is adding Author/Changed Date/Title to all <item>.<description> tags, eg: Anonymous (not verified) Sun, 03/17/2019 - 17:31 AI approach outperformed human experts in identifying cervical precancer

• RSS views do not show nodes in the correct language

  • Spanish titles display in English, nodes are rendered in English despite Content Revision.Language = Spanish in View Filter and Language selector.

• How to get feed title in correct language?

  • When viewing feed in spanish (requiring /espanol/ in front of URL) node titles are in English, though Body is in Spanish

• Content language of view row" rendering option does not work in rss feed display

  • Feed doesn't filter on language unless /espanol/ is being used

These are the patches in the Drupal 8.6 version Lightning Core

• 2869592 - Disabled update module shouldn't produce a status report warning
  • https://www.drupal.org/files/issues/2869592-remove-update-warning-7.patch
• 2885441 - EntityReferenceAutocompleteWidget should define its size setting as an integer
  • https://www.drupal.org/files/issues/2885441-2.patch
• 2815221 - Add quickedit to the latest-revision route
  • https://www.drupal.org/files/issues/2018-09-24/2815221-109.patch
• 1356276 - Allow profiles to define a base/parent profile and load them in the correct order
  • https://www.drupal.org/files/issues/2018-10-12/1356276-531.patch
• 2914389 - Allow profiles to exclude dependencies of their parent
  • https://www.drupal.org/files/issues/2018-07-09/2914389-8-do-not-test.patch