🇺🇸United States @Olarin

Yes, the latest version of the pull request seems to work properly for me, thanks.

Tried both the merge request and the patch in #4 (not at the same time of course). In either case, while I could successfully edit the text format again, when looking at the Markdown filter settings in the text format, the following error was displayed:

Error message
Drupal\markdown\Form\ParserConfigurationForm::buildParser(): Argument #2 ($form_state) must be of type Drupal\markdown\Form\SubformStateInterface, Drupal\Core\Form\SubformState given, called in /var/www/html/webroot/modules/markdown/src/Form/ParserConfigurationForm.php on line 239

Furthermore, if I save the text format (even without making changes), then it seems to break formatting entirely, i.e. a text field using Markdown is displayed without _any_ formatting, as in no HTML tags at all, not even line breaks or paragraphs. (Fortunately I tested this on a dev copy of a site and not a live site.) There are other filters at play on the site in question, but I tried turning all the rest of them off and confirmed that Markdown specifically is the one causing the formatting to be stripped (whereas if I turn Markdown off the text at least gets paragraphs and line breaks again, and the other filters can work as expected).

Olarin → created an issue.

quietone → credited Olarin → .

This appears to be a guaranteed issue for any new site audacious enough to attempt to use any install profile other than standard (including the core-provided minimal), and there's no workaround to my knowledge, so I think it would qualify as Major priority.

I added a MR for the 10.1.x branch. I'm not sure where to start on adding a relevant test.

Olarin → made their first commit to this issue’s fork.

PR created. I also fixed the outdated reference to "terms" (rather than entities) in the autocreate option description while I was at it.

Olarin → created an issue.