Problem/Motivation

When following the readme or documentation pages to add new parser libraries, the library is not available unless the markdown module is uninstalled and re-installed.

I think this could be as designed given the logic found in markdown_requirements(), but I'm not entirely sure.

Steps to reproduce

  • Enable module
  • Add new markdown library via composer, e.g. composer require michelf/php-markdown:^2.0
  • Go to /admin/config/content/markdown
  • Observe parser (e.g. PHP Markdown) is listed as unavailable
  • Expected behavior: parser is listed as available

Proposed resolution

TBD

Remaining tasks

  • Identify the root cause
  • Consider options
  • Choose options

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Comments

jasonawant created an issue. See original summary.

megachriz’s picture

megachriz
Primary language Dutch
commented

I experience that a cache rebuild is enough to make the parser available. I think that that behavior is okay, though it would be cool if that is mentioned on /admin/config/content/markdown as also said in #3259945: Help text at /admin/config/content/markdown should say that a cache clear is needed to pick up new parsers.

Shall we close this one as "works as designed"? Or does a cache rebuild not resolve the issue for you?

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Active » Closed (works as designed)

I will close this as there was no response to @megachriz in #2. Cleaning up the queue. Feel free to disagree with that take and I am happy to discuss further.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.