- 🇦🇺Australia interlated
Machine name: markdown
Version: 3.0.0-rc2Confirming that the path `/admin/config/content/markdown/PARSER/confirm-operation/default` seemed to set as needed in order to dismiss the false error.
If I visit /admin/config/content/markdown, I have one available parser: "Parsedown (default)". The fact that the word "default" is on this page indicates to me that Parsedown is the default parser.
However, if I run:
\Drupal::service('plugin.manager.markdown.parser')->getDefaultParser();
I get a warning:
[warning] No default markdown parser set, using first available installed parser "parsedown".
On a very busy site, this leads to dozens of warnings being logged _per second_.
On markdown.module, markdown_modules_installed() sets the config markdown.settings.default_parser when the markdown module is installed, but parsers may not be available at the moment markdown is installed; they may be installed after, which causes markdown.settings.default_parser to never be set.
The workaround is to run the following code:
drush ev "markdown_modules_installed(['markdown'])"
Then re-export your configuration (drush config:export), then import your configuration to the production site.
Install the module with no parsers available, and then add a parser using composer require, then run \Drupal::service('plugin.manager.markdown.parser')->getDefaultParser();
Do not log a warning,
Make sure the config markdown.settings.default_parser is set when new parsers are added.
None.
None.
None.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Machine name: markdown
Version: 3.0.0-rc2
Confirming that the path `/admin/config/content/markdown/PARSER/confirm-operation/default` seemed to set as needed in order to dismiss the false error.