Steps to reproduce
1. Installed rc1.
2. Configured the global markdown settings at /admin/config/content/markdown. Set "Render Strategy" to "Filter Output."
3. Configured markdown settings for my text format. Set "Render Strategy" to "None."
4. Check markdown settings for text format. "Render Strategy" is still "Filter Output."
I'm not sure if this automatic override is the intended behavior, but if it is, then the Render Strategy should not be configurable on the format.
To get "Render Strategy" to "None," it appears you must first go to the global settings and set to "Filter Output." This is confusing because there is no message on the input filter page that says that is necessary.
Comment | File | Size | Author |
---|---|---|---|
#6 | 3137201-6.patch | 8.95 KB | markhalliwell |
#6 | interdiff-3137201-5-6.txt | 828 bytes | markhalliwell |
Comments
Comment #2
ptmkenny CreditAttribution: ptmkenny commentedComment #3
markhalliwellSee if this works.
Comment #4
ptmkenny CreditAttribution: ptmkenny commentedI updated to the latest dev version, applied the patch, cleared the cache.
I can change the overall settings at /admin/config/content/markdown without problem. However, on the text format settings page, whenever I save the settings, it reverts to "Filter Output" no matter what I changed it to.
I tried unchecking the Markdown checkbox, saving the page, and then re-enabling it, but it is stuck on "Filter Output."
Comment #5
markhalliwellOk, try this one. I actually stepped through this one and was able to override the site-wide render strategy and rendered it correctly.
Comment #6
markhalliwellSigh... didn't manually re-test when there's a specific parser chosen; there's no "parser" array key, that's what it extracted.
Comment #7
ptmkenny CreditAttribution: ptmkenny commentedThanks, I could no longer reproduce the issue with #6!
Comment #9
markhalliwell