Fix fancybox & medium-zoom for hexo asset_img tag

[sankoshine]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines.
• Tests for the changes was maked (for bug fixes / features).
  • Mist have been tested.
  • Pisces have been tested.
• Docs in NexT website have been added / updated (for features).

PR Type

What kind of change does this PR introduce?

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Build related changes.
• CI related changes.
• Documentation content changes.
• Other... Please describe:

What is the current behavior?

Issue resolved: N/A

If I use hexo tag plugins to insert an image, it will not be rendered as medium zoom style.

i.e. {% asset_img 2222.jpg %}

What is the new behavior?

Medium zoom take effects on images whether imported with hexo asset_img tag or markdown-style ![](image.jpg).

• Screenshots with this changes: N/A
• Link to demo site with this changes: N/A

How to use?

Just set true.

In NexT _config.yml:

mediumzoom: true

Does this PR introduce a breaking change?

• Yes.
• No.

[welcome]

Thanks so much for opening your first PR here!

[CLAassistant]

All committers have signed the CLA.

[jiangtj]

Can you test whether <img> under <a> label is also managed by mediumzoom ?

Some users expect the link to work.

[stevenjoezhang]

And you can also fix fancybox in this PR

[sankoshine]

Can you test whether under label is also managed by mediumzoom ?

Some users expect the link to work.

Yes I have tested all following:

• {% asset_img a.jpg %}
• <img src="a.jpg" />
• ![](a.jpg)
• [{% asset_img a.jpg %}](https://site.com)
• <a href="https://site.com">{% asset_img 2222.jpg %}</a>
• [![](a.jpg)](https://site.com)

Each is working fine. MediumZoom on images with link won't be triggered.

[stevenjoezhang]

In fact, in the stylesheet of theme-next, .post-body > p > img is different from .post-body > img (with a margin of 20px)
Thus a better solution is to ask Hexo to fix the bug of asset_image tag: <img> should always be wrapped with <p>.

[jiangtj]

Thus a better solution is to ask Hexo to fix the bug of asset_image tag: <img> should always be wrapped with <p>.

This may be marked rendering problems, markdown-it is not the same with marked results.

[jiangtj]

Strange, the official demo normal, hexo-render-markd also unmodified {%%}

[stevenjoezhang]

There seems to be no more elegant solution

[welcome]

Congrats on merging your first pull request here! 🎉 How awesome!

[1v9]

@all-contributors please add @sankoshine for bug

[allcontributors]

@1v9

I've put up a pull request to add @sankoshine! 🎉