Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource view description is not rendered as Markdown #3128

Closed
torfsen opened this issue Jun 21, 2016 · 0 comments · Fixed by ckan/ckanext-pdfview#24
Closed

Resource view description is not rendered as Markdown #3128

torfsen opened this issue Jun 21, 2016 · 0 comments · Fixed by ckan/ckanext-pdfview#24

Comments

@torfsen
Copy link
Contributor

torfsen commented Jun 21, 2016

CKAN allows you to use Markdown in a resource view's description (mentioned explicitly below the description text area). However, CKAN 2.5.2 fails to render the description as Markdown and displays it as plain text instead.

torfsen added a commit to torfsen/ckan that referenced this issue Jun 21, 2016
Previously, CKAN rendered resource view descriptions as plain text, in
contrast to the help text given in the resource view edit form which
says that Markdown is supported.
amercader added a commit that referenced this issue Jun 21, 2016
…iption-as-markdown

[#3128] Render resource view descriptions as Markdown.
k-nut pushed a commit to k-nut/ckan that referenced this issue Jul 4, 2016
Previously, CKAN rendered resource view descriptions as plain text, in
contrast to the help text given in the resource view edit form which
says that Markdown is supported.
amercader pushed a commit that referenced this issue Aug 25, 2016
Previously, CKAN rendered resource view descriptions as plain text, in
contrast to the help text given in the resource view edit form which
says that Markdown is supported.

Conflicts:
	ckan/tests/controllers/test_package.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant