You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The giscus comment system won't work if its lang option is set to default (leaving "giscus:lang:" empty in _config.yml) AND site.lang is set to a language option with a language code followed by a country code, i.e. vi-VN, en-ES.
Instead of displaying a comment section, the IFrame displays "Giscus.app refused to connect".
Steps To Reproduce
Setup an app using chirpy theme in the given environment.
Create a sample post in that app.
Go to giscus.app and configure a repository for comments.
In _config.yml, set the following configs:
lang: vi-VN
...
comments:
provider: giscus...giscus:
... // The configs obtained from https://giscus.app/lang:
...
Build and serve the app
bundle exec jekyll s
Go to the sample post and scroll to the comment section.
Observe the bug: the for the comment section displays: "Giscus.app refused to connect".
After checking the giscus API, I noticed that the language codes for available languages never have a following country code, so the language options with the code of that type will cause the API call to fail.
The text was updated successfully, but these errors were encountered:
Checklist
How did you create the site?
Built from
jekyll-theme-chirpy
Describe the bug
The giscus comment system won't work if its lang option is set to default (leaving "giscus:lang:" empty in _config.yml) AND site.lang is set to a language option with a language code followed by a country code, i.e. vi-VN, en-ES.
Instead of displaying a comment section, the IFrame displays "Giscus.app refused to connect".
Steps To Reproduce
bundle exec jekyll s
Expected Behavior
The comment section displayed correctly
Environment
Anything else?
After checking the giscus API, I noticed that the language codes for available languages never have a following country code, so the language options with the code of that type will cause the API call to fail.
The text was updated successfully, but these errors were encountered: