Would you give us a updated example ?

[galaxy001]

Under https://github.com/settings/apps/, Webhook URL is required.

Under repo hooks, Payload URL is required. And which Content type should I choose ?

---

I have a blog at https://galaxysd.github.io/public/html/gpgc_redirect, and https://galaxysd.github.io/public/html/gpgc_redirect/index.html is a 404 page.

Now, I keep getting The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application error.

[galaxy001]

I got Refused to send form data to 'https://galaxysd.github.io/public/html/gpgc_redirect?code=abcdabcd1234&state=1234567890' because it violates the following Content Security Policy directive: "form-action 'self' github.com gist.github.com". after setting 'User authorization callback URL' to https://galaxysd.github.io/public/html/gpgc_redirect.

[wireddown]

Yes! I can, but likely in the first week of October.

[galaxy001]

Er, when is the scheduled time now?

[wireddown]

Stale links

Under https://github.com/settings/apps/

GitHub appears to have renamed some pages and portals. The setup page asks you to visit https://github.com/settings/applications (not apps), but using the newer GitHub settings page menu, the correct URL is now https://github.com/settings/developers , accessed via Settings > Developer Settings > OAuth Apps.

Webhook URL is required. Under repo hooks, Payload URL is required. And which Content type should I choose ?

For OAuth applications, these are not applicable, and they are not on the settings page:

Symptom

When I visited your blog, I saw the generic error message. I'll gather some information from your profile and blog and see if I can identify the problem and fix without needing the diagnostics.

[wireddown]

Red error message

Watching your blog page load, the error message in the red <div> appears when gpgc searches GitHub for an issue in your blog repository with the same title as the blog post but receives zero results. This is consistent with what I found in the repository:

• Blog post: https://galaxysd.github.io/story/20171016/AntFortune-AD
• Blog source: https://github.com/galaxysd/galaxysd.github.io/blob/master/_posts/2017-10-16-AntFortune-AD.md
• Blog title: 支付宝蚂蚁财富“扎心文案”广告：“年纪越大，越没有人会原谅你的穷！”
• Blog issues: https://github.com/galaxysd/galaxysd.github.io/issues
  NOTE: none of the issues have a matching title

When I inspect one of the issues, it looks like the gpgc script that creates issues as posts are pushed uses the wrong URL format for your blog repository.

• Blog issue: 计算序列的N50、N90等 galaxysd/galaxysd.github.io#6
• Blog issue source URL: https://galaxysd.github.io/2012/03/26/2012-03-26-cal-n50-n90.md
• Blog live URL: https://galaxysd.github.io/bioinformatics/20120326/cal-n50-n90

Specifically, the script doesn't know how Jekyll has mutated the URL structure from 2012/03/26/2012-03-26-cal-n50-n90.md to bioinformatics/20120326/cal-n50-n90. I suspect these are related to the permalink and other configuration settings in your blog's _config.yml file. Right now, the script uses a hardcoded format: ${site}/${year}/${month}/${day}/${post_slug}.

This bug, however, is not responsible for your original issue.

Login errors

I was not able to reproduce your problem. Rather, the opposite happened. I was able to login to GitHub, so that I could see my user image, but when I tried to preview or post a comment, I received a different error message: "Resource not accessible by integration".

Returning to the GitHub developer documentation, it appears that the link URLs in my earlier comment were foreshadowing a larger problem: GitHub now distinguishes between OAuth apps and GitHub apps, and I believe gpgc is using the wrong flavor. Instead of being an OAuth app, the comment system now needs to be a GitHub app.

There is a lot more reading I need to do, and I'm worried it will take a while for me to provide an update.

[wireddown]

The situation might not be so dire :-)

It looks like GitHub has tuned their scope access levels. Previously, public_repo was sufficient to search for and comment on issues on public repositories, but it appears that repo is now the new access level.

[wireddown]

So, I think there are two changes necessary to fix this problem for you:

1. Update the setup documentation to guide users to create a GitHub OAuth application.
2. Update gpgc_core.js to request repo scope instead of public_repo scope.

[galaxy001]

Yes, I am facing this, many settings are in the repo settings instead of user settings.

Looking forward to your updated guide.

[kioli]

Hi @galaxy001
I just went to your blog and tried to post a comment, and the log in button at the bottom redirected me to a page where I had to confirm my github identity and then it rightfully brought me back to the post comment section and the button changed from "log in" to "post" :)

Unfortunately that is not the case for me and my blog

I'd like to know what am I doing wrong since when I try to post a comment I get redirected to an authentication page but then when I put my credentials I go to my blog homepage with an url reporting "error redirect url mismatch state"...

I followed the guide on how to configure the files but I am not sure if the error is now in Heroku, in the github OAUTH specs for the "Authorization callback URL" or in the .yml files... could you please help? :)
many thanks

p.s. also if you @wireddown could quickly tip me off for where I am going wrong that'd be sweet

[wireddown]

Hi @kioli, I did not encounter any problems with your setup.

I was able to login, preview, and post a comment to this post: https://kioli.github.io/android/2017/03/17/Git-CLI-shortcut/ .

Perhaps you browser cache is interfering. What happens after you delete your local cache?

[galaxy001]

Hi @wireddown, I patched the script for permalink, but there are still bugs and now I get a lot of github issues with same title.

I think it will be better if the script can use a fixed list file to map posts to issue numbers. So that we can overwrite/update those issues. As there is no way to remove an issue without removing the entire repo.

The script can query for issues that tagged Post Comments and has no reply for an initial list of available issue number, after inserting new issue number for more posts, write the whole list for us to modify. Then read the list to overwrite each specified issue.

[wireddown]

Thanks for sharing these use cases! Would you mind adding a little more detail about what you mean by overwrite and update?

Do you want to use a new issue with an old post? Do you want to reorder the issues?

What is the state with the error messages you have been seeing when trying to login or post comments? Is the local script the last area with misbehavior?

[galaxy001]

The local script stops at a first item with [] in the title.
And each time I run it, it successfully creates a new issue with the same title.

I'll write a new issue for this feature request. #33

[wireddown]

Thanks :-)

What is the state with the error messages you have been seeing when trying to login or post comments? Is the local script the last area with misbehavior?