next-theme / hexo-theme-next

๐ŸŽ‰ Elegant and powerful theme for Hexo.
https://theme-next.js.org
Other
2.44k stars 432 forks source link

utterances doesn't work for me #433

Closed wasi-master closed 2 years ago

wasi-master commented 2 years ago

Issue Checklist


Expected behavior

The repo parameter of the url for the iframe should contain the full repo name including the author (wasi-master/blog) instead of just the repo name (blog).

Actual behavior

The repo parameter of the url for the iframe should contains just the repo name, blog, utterances can't work with that since different users can have a repo with the same name. I tried using inspect element to change it to wasi-master/blog and then it worked perfectly (See screenshots)

Steps to reproduce the behavior

For me just putting the repository name (wasi-master/blog) was enough. I tried blog to no avail

Environment Information

Node.js and NPM Information

v16.8.0
7.24.0

Package dependencies Information

hexo-site@0.0.0 C:\Users\Wasi Master\Documents\GitHub\blog\website
โ”œโ”€โ”€ hexo-algoliasearch@1.0.0
โ”œโ”€โ”€ hexo-autonofollow@1.0.1
โ”œโ”€โ”€ hexo-browsersync@0.3.0
โ”œโ”€โ”€ hexo-deployer-git@3.0.0
โ”œโ”€โ”€ hexo-generator-archive@1.0.0
โ”œโ”€โ”€ hexo-generator-category@1.0.0
โ”œโ”€โ”€ hexo-generator-feed@3.0.0
โ”œโ”€โ”€ hexo-generator-index@2.0.0
โ”œโ”€โ”€ hexo-generator-tag@1.0.0
โ”œโ”€โ”€ hexo-next-share@1.1.0 (git+ssh://git@github.com/theme-next/hexo-next-share.git#a0cfd32ade7bd25b8d282366fa177afb7644d321)      
โ”œโ”€โ”€ hexo-renderer-ejs@2.0.0
โ”œโ”€โ”€ hexo-renderer-marked@4.1.0
โ”œโ”€โ”€ hexo-renderer-stylus@2.0.1
โ”œโ”€โ”€ hexo-server@2.0.0
โ”œโ”€โ”€ hexo-theme-landscape@0.0.3
โ”œโ”€โ”€ hexo-word-counter@0.0.3 (git+ssh://git@github.com/next-theme/hexo-word-counter.git#30d288d5c0d40f4174852194ddb225d901fb6525)  
โ”œโ”€โ”€ hexo-wordcount@6.0.1
โ””โ”€โ”€ hexo@6.0.0

Hexo Configuration

_config.yml - https://github.com/wasi-master/blog/blob/main/website/_config.yml _config.next.yml - https://github.com/wasi-master/blog/blob/main/website/_config.next.yml#L667-L673

NexT Configuration

_config.yml - https://github.com/wasi-master/blog/blob/main/website/_config.yml _config.next.yml - https://github.com/wasi-master/blog/blob/main/website/_config.next.yml#L667-L673

Other Information

Here's the link it generated

Raw:

https://utteranc.es/utterances.html?crossorigin=anonymous&repo=blog&issue-term=pathname&theme=github-dark&src=https%3A%2F%2Futteranc.es%2Fclient.js&url=http%3A%2F%2Fwasi-master.github.io%2Fblog%2F&origin=http%3A%2F%2Flocalhost%3A4000&pathname=blog%2F2022%2F01%2F02%2Fhow-i-learn-new-programming-languages%2F&title=How%20Do%20I%20Learn%20New%20Programming%20Languages%20So%20Easily%3F%20%7C%20Wasi%20Master's%20Blog&description=The%20personal%20blog%20of%20Wasi%20Master%20aka.%20Arian%20Mollik%20Wasi&og%3Atitle=Wasi%20Master's%20Blog

Prettified

https://utteranc.es/utterances.html

crossorigin : anonymous
repo        : blog
issue-term  : pathname
theme       : github-dark
src         : https://utteranc.es/client.js
url         : http://wasi-master.github.io/blog/
origin      : http://localhost:4000
pathname    : blog/2022/01/02/how-i-learn-new-programming-languages/
title       : How Do I Learn New Programming Languages So Easily? | Wasi Master's Blog
description : The personal blog of Wasi Master aka. Arian Mollik Wasi
og:title    : Wasi Master's Blog

As you can see above, repo: blog where it should have been repo: wasi-master/blog

Additional bugs

stevenjoezhang commented 2 years ago

Thanks for your feedback. The documentation of utterances in _config.yml and our website is not clear, I'll update it later.

wasi-master commented 2 years ago

Thanks for the response, looking forward to it.

wasi-master commented 2 years ago

Well can you at least tell me what was wrong in my case? That would be really helpful :)

stevenjoezhang commented 2 years ago

Docs updated: https://github.com/next-theme/hexo-theme-next/commit/1b8f1e217f0dcc98a19a4bd32cc0621177fd4489

About the additional bugs, Gitalk is working on my website.

github-actions[bot] commented 1 year ago

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.