Troubleshooting

Keep up indentation

When you edit any YAML configs, always need to keep up indents.
Currently, in all Hexo and NexT configuration files parameters uses 2 spaces indents from parent option.

For example, we want to change NexT scheme from standart Muse to Gemini and want to use Data Files feature with Hexo way option.

We open theme config file and under the «Scheme Settings» section copy next parameters:

next/_config.yml
# ---------------------------------------------------------------
# Scheme Settings
# ---------------------------------------------------------------

scheme: Muse
#scheme: Mist
#scheme: Pisces
#scheme: Gemini

Then we open site config file and paste these parameters under theme_config section:

hexo/_config.yml
theme_config:

#scheme: Muse
#scheme: Mist
#scheme: Pisces
scheme: Gemini

Here will nothing happen because indentation not keeped up. Hexo just can't see these parameters because subparameters (children parameters of theme_config parameter) are not exists. Let's see same configuration with indents.

hexo/_config.yml
theme_config:

#scheme: Muse
#scheme: Mist
#scheme: Pisces
scheme: Gemini

And here Hexo can read these parameters as theme_config.scheme: Gemini in same way, as NexT can read scheme: Gemini parameter. So, with 2 spaces indents from parent option(s) Hexo will load all NexT parameters and work fine.

Backtick Code Block in Tags

For Hexo before version 4.0, when backtick code block(s) exists inside other tags (like blockquote, note, tabs), that code block will be generated as «undefined» string in HTML. There are several ways to resolve this:

Instead of Backtick Code Block you also can use tagged Code Block.
But in rare cases standard code block can obtain errors inside other tags.

Use HTML tags instead of Hexo tags: <pre><code>.
In this case you can't add code syntax highlighting.

Here is the PR with bugfix for backtick code block inside tags (Submitted in 2016, merged three years later).
So, upgrade to Hexo 4.0 or higher, if you need to use backtick code block inside tags.

Sometimes during generate you can see «Error: Unmatched placeholder remains!» message.
This mean somewhere in your posts, blocks with tags was commented with {# and #} symbols:

{% raw %}{#
{% label error@Unmatched placeholder remains! %}
#}{% endraw %}
{% raw %}
{% label error@Unmatched placeholder remains! %}
{% endraw %}

Favicon Set but Doesn't Work (Need to redocs)

Put your favicon under site's source dir. If you find that your Favicon doesn't work, please clean your browser's cache first and then visit your Favicon's URL directly, which should be http(s)://your-domain.com/favicon.ico.

If your site is in a subdirectory please set it to favicon: favicon.ico.

TOC Issues

Do not hava a skip-level directory in the post. For example, a third level directory ### followed by a ##### is not recommended.
See: https://github.com/theme-next/hexo-theme-next/issues/882

If you are using hexo-renderer-markdown-it, it's recommended to install markdown-it-named-headings to make the TOC work correctly.

npm install markdown-it-named-headings

See: https://github.com/theme-next/hexo-theme-next/issues/1168
Here is the PR with bugfix for default config of hexo-renderer-markdown-it plugin.