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

当设置 related_posts: params: isDate: true 后在特定条件下会导致 hexo g 运行失败 #1456

Open
3 tasks done
st1020 opened this issue Apr 9, 2020 · 5 comments
Labels

Comments

@st1020
Copy link

st1020 commented Apr 9, 2020

Issue Checklist

  • I am using the latest version of NexT.
  • I have read the relevant documents of Hexo and NexT.
  • I have reviewed the latest Roadmap on GitHub and searched for current issues, which does not help me.

Expected behavior

在主题配置文件中进行以下设置后,能够正常运行 hexo g

related_posts:
  enable: true
  params:
    isDate: true

Actual behavior

进行如上设置,且博客中存在两篇具有相同 tag 的博文时,会导致运行 hexo g 出现 ERROR Cannot read property 'replace' of null错误

Steps to reproduce the behavior

  1. 进行如上设置并安装相关依赖
  2. 添加两篇 tag 相同的博文
  3. 运行 hexo g

Environment Information

Node.js and NPM Information

v13.12.0
6.14.4

Package dependencies Information

Hexo Configuration

全部保持默认即可重现错误

NexT Configuration

related_posts:
  enable: true
  params:
    isDate: true
@st1020 st1020 added the Bug label Apr 9, 2020
@welcome
Copy link

welcome bot commented Apr 9, 2020

Thanks for opening this issue, maintainers will get back to you as soon as possible!

@st1020
Copy link
Author

st1020 commented Apr 9, 2020

没有人知道我为了定位到这个错误用了多长的时间😭😭😭

@hui-shao
Copy link

hui-shao commented May 7, 2020

我遇到同样的问题了,只要设置:

related_posts:
  enable: true

就会在生成时报错
#1498

@wangworld
Copy link

可暂时屏蔽isDate参数

@sli1989
Copy link
Collaborator

sli1989 commented Aug 27, 2020

can u check this tea3/hexo-related-popular-posts#27 (support hexo 5.0.0)?

@sli1989 sli1989 added Question and removed Bug labels Aug 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants