hexo s打不开页面
Unhandled rejection TypeError: path.substring is not a function
at Object.urlForHelper (。。。\hexo\node_modules\hexo\lib\plugins\helper\url_for.js:7:31)
at wrapper (。。。\hexo\node_modules\lodash\lodash.js:4949:19)
用landscape原生主题没问题。
v8.11.1
5.6.0
hexo init,clone next主题,把原来保存的source文件夹拷贝过来,设置hexo的config文件的主题,hexo s。
{
"name": "hexo-site",
"version": "0.0.0",
"private": true,
"hexo": {
"version": "3.7.1"
},
"dependencies": {
"hexo": "^3.2.0",
"hexo-generator-archive": "^0.1.4",
"hexo-generator-category": "^0.1.3",
"hexo-generator-index": "^0.2.0",
"hexo-generator-tag": "^0.2.0",
"hexo-renderer-ejs": "^0.3.0",
"hexo-renderer-stylus": "^0.3.1",
"hexo-renderer-marked": "^0.3.0",
"hexo-server": "^0.2.0"
}
}
hexo: 3.7.1
hexo-cli: 1.1.0
os: Windows_NT 10.0.16299 win32 x64
http_parser: 2.8.0
node: 8.11.1
v8: 6.2.414.50
uv: 1.19.1
zlib: 1.2.11
ares: 1.10.1-DEV
modules: 57
nghttp2: 1.25.0
openssl: 1.0.2o
icu: 60.1
unicode: 10.0
cldr: 32.0
tz: 2017c
没有修改过
NexT Version:
NexT Scheme:
没有修改过
maybe caused by the unusual update. How about delete the local folds and new init?
@sli1989 I've tried newly init and copy my source folder into new hexo, what I've said is happend after newly init.
Use the next v6 version?
Can provide the living link of your source folder?
@FannyChung I meet same error. Are you use next.yml? I find many value's field has bean changed between V5+ and V6. For example: since,favicon. You can compare your files careful and find the difference. For me, I worked.
@wt1098078873 Thank you! But I use a new hexo fold, just copy my source fold(including my .md and pictures) , I didn't change yml file.
@sli1989 here's my source folder. https://1drv.ms/f/s!AmqC5vM1N-zd-QQDTFMgDqBJGc1T
DId u use next.yml in v5 without download the v6 files?
I saw u mixed the configuration. How about use v6 separately and set the next.yml comparing the next v6 yml with your custom setting before?
This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I believe this issue is caused by a malformed _config.yml.
Most helpful comment
@FannyChung I meet same error. Are you use
next.yml? I find many value's field has bean changed betweenV5+andV6. For example:since,favicon. You can compare your files careful and find the difference. For me, I worked.