In current form the Basic HTML filter is set to UND for the language which prevents it from being translated. This produces an "Access denied" message on the translation page for Basic HTML.

This issue has been dealt with in the past in #1935000: Some configuration entities are created as in language unknown and #1947814: New config entities often save as langcode: und incorrectly.

To see this bug in action you must enable, which will eventually be merged with core. Reinstall after applying patch and/or copy the affected files to your staged config and then sync config.

filter-format-basic-html-needs-default-language.patch795 bytesAnonymous (not verified)
PASSED: [[SimpleTest]]: [MySQL] 57,156 pass(es). View
Members fund testing for the Drupal project. Drupal Association Learn more


Anonymous’s picture

Status: Active » Needs review
YesCT’s picture

Status: Needs review » Reviewed & tested by the community

code changes are good, just enough to fix.

I tested it manually also, and it lets the config_translation module do what it is trying to do. (I mean it can try to translate them, when they have the actual language and not und.)

YesCT’s picture

Issue tags: +D8MI, +sprint, +language-config

tagging to be tidy

Gábor Hojtsy’s picture

Title: Filter format Basic HTML needs a default language so it can be translated » Basic HTML and plain HTML should ship as English configuration

Retitled slightly. Agree with RTBC. We did the same thing to lots of other config, and the rest of the filter formats are 'en' already.

YesCT’s picture

Issue tags: +Quick fix


alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed 86bc222 and pushed to 8.x. Thanks!

Wim Leers’s picture

Component: node.module » filter.module
Issue tags: -sprint

Lovely! I wish I knew about this, then I'd have done it this way originally. Maybe things changed around this after it got committed? In any case: thanks! :)

Automatically closed -- issue fixed for 2 weeks with no activity.