-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
使用Gitalk但无法评论,并提示"Error: Not Found." #142
Labels
🍰 Usage problem
Some usage problems
Comments
你有没有初始化?
…---原始邮件---
发件人: "weigr"<notifications@github.com>
发送时间: 2020年12月19日 21:29:18
收件人: "liuyib/hexo-theme-stun"<hexo-theme-stun@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: [liuyib/hexo-theme-stun] 使用Gitalk但无法评论,并提示"Error: Not Found." (#142)
我想创建一个新的 issue
是的,我已经阅读了 常见问题。
是的,我搜索并阅读了 Issues 列表(包括关闭的),但是没有帮助到我。
是的,我是第一次使用 Stun 主题。
是的,我之前用过 Stun 主题,并且可以正常运行。但是当我启用Gitalk开启评论后,无法进行评论,页面一直显示"Error: Not Found"。
[] 是的,我使用了 平滑升级 的特性,并且阅读了其文档。
环境信息
Stun 版本: 1.7.0
**Hexo 版本:4.2.0
平台信息: win10 专业版
浏览器信息:
Node.js 和 NPM 版本:
PS D:\hexo> node -v
v12.16.1
PS D:\hexo> npm -v
6.13.4
NPM 依赖信息:
hexo-site@0.0.0 D:\hexo
+-- hexo@4.2.0
+-- hexo-deployer-git@2.1.0
+-- hexo-generator-archive@1.0.0
+-- hexo-generator-category@1.0.0
+-- hexo-generator-index@1.0.0
+-- hexo-generator-search@2.4.0
+-- hexo-generator-tag@1.0.0
+-- hexo-render-pug@2.1.4
+-- hexo-renderer-ejs@1.0.0
+-- hexo-renderer-marked@2.0.0
+-- hexo-renderer-stylus@1.1.0
+-- hexo-server@1.0.0
`-- hexo-wordcount@6.0.1
Hexo 配置信息:
查看代码 ...
Stun 配置信息:
查看代码 ... gitalk: enable: true # Github username. owner: HYSWZW # Github repository. repo: https://github.com/HYSWZW/Comment # Github Application Client ID. client_id: b3620a1***1cee97eb # Github Application Client Secret. client_secret: 77aa4a3c2f297df767***9775d164d300b0cfb # GitHub repo owner and collaborators, only these guys can initialize github issues. admin: HYSWZW # Facebook-like distraction free mode. distraction_free_mode: true # Gitalk's display language depends on user's browser or system environment. # If you want everyone visiting your site to see a uniform language, you can set a force language value. # Optional values: en | zh-CN | es-ES | fr | ru | zh-TW language: zh-CN
预期行为
实际行为
重现步骤
xxx
xxx
xxx
其他信息
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
你去网上搜索找下 “gitalk 初始化” 如果还解决不了再来这里说下情况。
…---原始邮件---
发件人: "weigr"<notifications@github.com>
发送时间: 2020年12月19日 21:29:18
收件人: "liuyib/hexo-theme-stun"<hexo-theme-stun@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: [liuyib/hexo-theme-stun] 使用Gitalk但无法评论,并提示"Error: Not Found." (#142)
我想创建一个新的 issue
是的,我已经阅读了 常见问题。
是的,我搜索并阅读了 Issues 列表(包括关闭的),但是没有帮助到我。
是的,我是第一次使用 Stun 主题。
是的,我之前用过 Stun 主题,并且可以正常运行。但是当我启用Gitalk开启评论后,无法进行评论,页面一直显示"Error: Not Found"。
[] 是的,我使用了 平滑升级 的特性,并且阅读了其文档。
环境信息
Stun 版本: 1.7.0
**Hexo 版本:4.2.0
平台信息: win10 专业版
浏览器信息:
Node.js 和 NPM 版本:
PS D:\hexo> node -v
v12.16.1
PS D:\hexo> npm -v
6.13.4
NPM 依赖信息:
hexo-site@0.0.0 D:\hexo
+-- hexo@4.2.0
+-- hexo-deployer-git@2.1.0
+-- hexo-generator-archive@1.0.0
+-- hexo-generator-category@1.0.0
+-- hexo-generator-index@1.0.0
+-- hexo-generator-search@2.4.0
+-- hexo-generator-tag@1.0.0
+-- hexo-render-pug@2.1.4
+-- hexo-renderer-ejs@1.0.0
+-- hexo-renderer-marked@2.0.0
+-- hexo-renderer-stylus@1.1.0
+-- hexo-server@1.0.0
`-- hexo-wordcount@6.0.1
Hexo 配置信息:
查看代码 ...
Stun 配置信息:
查看代码 ... gitalk: enable: true # Github username. owner: HYSWZW # Github repository. repo: https://github.com/HYSWZW/Comment # Github Application Client ID. client_id: b3620a1***1cee97eb # Github Application Client Secret. client_secret: 77aa4a3c2f297df767***9775d164d300b0cfb # GitHub repo owner and collaborators, only these guys can initialize github issues. admin: HYSWZW # Facebook-like distraction free mode. distraction_free_mode: true # Gitalk's display language depends on user's browser or system environment. # If you want everyone visiting your site to see a uniform language, you can set a force language value. # Optional values: en | zh-CN | es-ES | fr | ru | zh-TW language: zh-CN
预期行为
实际行为
重现步骤
xxx
xxx
xxx
其他信息
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@HYSWZW 问题解决了吗?如果解决了麻烦把 Issue 关了吧,因为我不确定你是否解决了问题。 |
我马上去试试,谢谢大佬
…------------------ 原始邮件 ------------------
发件人: "liuyib/hexo-theme-stun" <notifications@github.com>;
发送时间: 2020年12月20日(星期天) 下午3:09
收件人: "liuyib/hexo-theme-stun"<hexo-theme-stun@noreply.github.com>;
抄送: "248761724"<248761724@qq.com>;"Mention"<mention@noreply.github.com>;
主题: Re: [liuyib/hexo-theme-stun] 使用Gitalk但无法评论,并提示"Error: Not Found." (#142)
@HYSWZW 问题解决了吗?如果解决了麻烦把 Issue 关了吧,因为我不确定你是否解决了问题。
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Gitalk 需要先初始化 |
对滴 👌 |
灰常感谢,
…------------------ 原始邮件 ------------------
发件人: "EvanOne(文一)"<notifications@github.com>;
发送时间: 2020年12月20日(星期天) 下午3:52
收件人: "liuyib/hexo-theme-stun"<hexo-theme-stun@noreply.github.com>;
抄送: "248761724"<248761724@qq.com>; "State change"<state_change@noreply.github.com>;
主题: Re: [liuyib/hexo-theme-stun] 使用Gitalk但无法评论,并提示"Error: Not Found." (#142)
对滴 👌
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
我想创建一个新的 issue
环境信息
Stun 版本: 1.7.0
**Hexo 版本:4.2.0
平台信息: win10 专业版
浏览器信息:
Node.js 和 NPM 版本:
PS D:\hexo> node -v
v12.16.1
PS D:\hexo> npm -v
6.13.4
NPM 依赖信息:
hexo-site@0.0.0 D:\hexo
+-- hexo@4.2.0
+-- hexo-deployer-git@2.1.0
+-- hexo-generator-archive@1.0.0
+-- hexo-generator-category@1.0.0
+-- hexo-generator-index@1.0.0
+-- hexo-generator-search@2.4.0
+-- hexo-generator-tag@1.0.0
+-- hexo-render-pug@2.1.4
+-- hexo-renderer-ejs@1.0.0
+-- hexo-renderer-marked@2.0.0
+-- hexo-renderer-stylus@1.1.0
+-- hexo-server@1.0.0
`-- hexo-wordcount@6.0.1
Hexo 配置信息:
查看代码 ...
Stun 配置信息:
查看代码 ...
预期行为
实际行为
重现步骤
其他信息
The text was updated successfully, but these errors were encountered: