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

图片显示问题 [solved] #394

Closed
youngjuning opened this issue Aug 23, 2018 · 8 comments
Closed

图片显示问题 [solved] #394

youngjuning opened this issue Aug 23, 2018 · 8 comments
Labels

Comments

@youngjuning
Copy link

youngjuning commented Aug 23, 2018

image

@youngjuning
Copy link
Author

这是一个可点击的图片,我不想让他是 fancybox,请问我该怎么写

@maple3142
Copy link
Contributor

Do you mean how to prevent the img in an anchor from being wrapped as fancybox?

@youngjuning
Copy link
Author

@maple3142 yes

@youngjuning
Copy link
Author

image
当一篇文章同时属于两个分类,其中一个分类会是另一个分类的子分类。
image

@KaitoHH
Copy link
Contributor

KaitoHH commented Aug 23, 2018

@youngjuning commented on 2018年8月23日 GMT+8 上午10:53:

image

当一篇文章同时属于两个分类,其中一个分类会是另一个分类的子分类。

image

That is default behavior of Hexo. You can wrap these with brackets to define on the same hierarchical level.

categories:
  - [category1]
  - [category2]

refer this for detailed.

@Ahaochan
Copy link

+1, My Blog has same issue.
Even if I use <img> Tag to replace ![](https://img.shields.io/github/stars/Ahaochan/Tampermonkey.svg), The <img> Tag still wrapped as fancybox.

<img src="https://img.shields.io/github/stars/Ahaochan/Tampermonkey.svg" alt="star" style="display: inline;margin-bottom: -1%;">

Raincal pushed a commit that referenced this issue Nov 7, 2018
@Raincal
Copy link
Member

Raincal commented Nov 7, 2018

@youngjuning @Ahaochan Fixed in #468

@Raincal Raincal closed this as completed Nov 9, 2018
@ivan-nginx ivan-nginx changed the title 图片显示问题 图片显示问题 [solved] Mar 4, 2019
tongluyang pushed a commit to tongluyang/hexo-theme-next that referenced this issue Nov 19, 2019
@lock
Copy link

lock bot commented Mar 10, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Mar 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants