-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Markdown files are not rendered as expected #4087
Labels
bug
Something isn't working
Comments
2 tasks
I can reprocude this issue with pure Hexo (without hexo-theme-next). ## Quote
{% pullquote %}foo foo foo{% endpullquote %}
test001
{% pullquote %}bar bar bar{% endpullquote %}
## Insert
{% youtube https://example.com/demo.mp4 %}
test002
{% youtube https://example.com/sample.mp4 %} |
2 tasks
2 tasks
This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale. Test cases need to be updated to see if the issue has been solved. |
Relevant issues |
SukkaW
added a commit
to SukkaW/hexo
that referenced
this issue
Jun 19, 2020
SukkaW
added a commit
that referenced
this issue
Jun 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check List
Please check followings before submitting a new issue.
hexo version
to check)Expected behavior
When I used the hexo-theme-next video tag and other tags in the same markdown file, only the video tag rendered successfully and the other tags cannot be rendered. But if you remove the video tag, it will render properly.
I reported the bug to hexo-theme-next, but they said it was a hexo problem.
theme-next/hexo-theme-next#1353 (comment)
Actual behavior
How to reproduce?
You can clone the source code of this blog for reproduction: https://github.com/hujinbo/hexo-next-test
tagPluginTest.md
hexo server
Environment & Settings
Node.js & npm version
Your site
_config.yml
(Optional)Your theme
_config.yml
(Optional)Hexo and Plugin version(
npm ls --depth 0
)Your package.json
package.json
Others
The text was updated successfully, but these errors were encountered: