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.
We open theme config file and under the «Scheme Settings» section copy next parameters:
Then we open site config file and paste these parameters under
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.
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 must loaded any NexT parameters and worked fine.
When backtick code block(s) exists inside other tags (like
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:
In this case you can't add code syntax highlighting.
Here is pull with bugfix for use backtick code block inside tags (from Dec 2016 still not merged).
So, for this moment you can merge it manually, 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
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
If your site is in a subdirectory please set it to
NexT's tag plugin uses some submodules of Hexo, like
hexo-util. NPM uses new module install mode in version 3, NexT will use this mode which means if you are using a old NPM will find this error. So if you find error like "Cannot find module XXX", please use
npm -v to check your NPM version.
- Version > 3: Still not work? Please remove
node_modulesdirectory and reinstall using
- Version < 3:
- You can update your NPM
- Or can install modules (and their dependences) manually:
npm install --save hexo-util; where
hexo-utilis a example, please replace it with module name in the error.