Skip to content
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

"Application error" when trying to connect a new repository #296

Open
nverinaud opened this issue Jun 7, 2019 · 17 comments

Comments

@nverinaud
Copy link

commented Jun 7, 2019

I try to connect Staticman to my repository (Step 1 of "Getting Started") but it fails with an error from Heroku.

Here is the URL I call : https://api.staticman.net/v2/connect/Ryfacto/academie.ryfacto.fr.

And the response :

<!DOCTYPE html>
<html>
    <head>
        <meta name="viewport" content="width=device-width, initial-scale=1">
        <meta charset="utf-8">
        <title>Application Error</title>
        <style media="screen">
		  html,body,iframe {
			margin: 0;
			padding: 0;
		  }
		  html,body {
			height: 100%;
			overflow: hidden;
		  }
		  iframe {
			width: 100%;
			height: 100%;
			border: 0;
		  }
		</style>
    </head>
    <body>
        <iframe src="//www.herokucdn.com/error-pages/application-error.html"></iframe>
    </body>
</html>

Thanks a lot for your help !

@deadlydog

This comment has been minimized.

Copy link

commented Jun 14, 2019

I'm also having this same issue.

image

image

I'm not sure if it's related, but I noticed that the build is also failing. Perhaps a bad version got pushed out?

@deadlydog

This comment has been minimized.

Copy link

commented Jun 14, 2019

I found issue #243 and installed the app instead of going the contributor route. I think this (using v3) is the new recommended practice, but the docs have not been updated yet.

@huobi-registraciya

This comment has been minimized.

Copy link

commented Jun 14, 2019

I'm also having this same issue!

@askurashev

This comment has been minimized.

Copy link

commented Jun 22, 2019

I'm too.

@ayaxxchanz

This comment has been minimized.

Copy link

commented Jun 30, 2019

Hi. Any fix to this problem? I try to install Staticman with my Hugo site but always got this same error. The documentation is outdated. I also came across with several websites to ask questions about this but every time I want to post a comment, I receive this application error too (including the demo site https://hugo.staticman.net/ )

@tomasparks

This comment has been minimized.

Copy link

commented Jul 5, 2019

me too

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Jul 5, 2019

@ayaxxchanz The official Hugo + Staticman demo site is using the official developement API instance v2. Perhaps commit d800786 breaks support for v2, despite the project owner's intention to remain support for v1 & v2 (see below).

Edited: for a fix, you might consider #285.

@tomasparks Please avoid duplicating issues to keep discussion focused.

I found issue #243 and installed the app instead of going the contributor route. I think this (using v3) is the new recommended practice, but the docs have not been updated yet.

@deadlydog That's against what the project owner's idea in #243 (comment), so I don't think that's recommended by collaborators who don't wish to break current support and interupt the service, in light of @staticmanapp's huge "contributions" on GitHub.

@zxdawn2

This comment has been minimized.

Copy link

commented Jul 9, 2019

@VincentTam I can't find staticmanapp on GitHub:
image

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Jul 9, 2019

@zxdawn2 I don't own the official instance, so nobody can fix this except the author. You may try using an alternative instance (i.e. anything that's NOT official), like @staticmanlab, @staticmanaima, @BloggerBust-bot, etc.

P.S. I maintain the first one, and I helped the setup of the 2nd one through GitHub issues. I've only tested mine. If you want to use mine, please refer to the later half of einsteinpy/blog.einsteinpy.org#12 (comment) and adapt it to your repo. I'm too lazy to retype everything again. Please don't hesitate to ping me in case of questions.

@zxdawn2

This comment has been minimized.

Copy link

commented Jul 11, 2019

@VincentTam I tried to visit https://staticman3.herokuapp.com/v3/connect/github/zxdawn2/zxdawn2.github.io/master/comments, but I get this error:

Cannot GET /v3/connect/github/zxdawn2/zxdawn2.github.io/master/comments

BTW, I use this method to add comments:

<form method="POST" action="https://staticman3.herokuapp.com/v3/connect/github/{{ .Site.Params.staticman.username }}/{{ .Site.Params.staticman.repository }}/{{ .Site.Params.staticman.branch }}/comments">

As a result, when I try to post, I got this error:

Cannot POST /v3/connect/github/zxdawn2/zxdawn2.github.io/master/comments
@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Jul 11, 2019

@zxdawn2 Thanks for your invitation to @staticmanlab.

  1. The link for accepting the invitation is
    https://staticman3.herokuapp.com/v3/connect/github/zxdawn2/zxdawn2.github.io/
    Explanation: You invite a GitHub/GitLab user to the whole repo, not just to a particular branch.

  2. To hook up your HTML form with Staticman API. you need /entry instead of /connect.

    <form method="POST" action="https://staticman3.herokuapp.com/v3/entry/github/{{ .Site.Params.staticman.username }}/{{ .Site.Params.staticman.repository }}/{{ .Site.Params.staticman.branch }}/comments">
    

    Note that comments is just a property name in staticman.yml. You may change it to any name you like. For example, https://github.com/okfde/offenerhaushalt.de/blob/gh-pages/staticman.yml.

@zxdawn2

This comment has been minimized.

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Aug 3, 2019

@VincentTam thanks!
Although comment works, subscribe button doesn't work:
https://github.com/zxdawn2/zxdawn2.github.io/blob/3a9b470ddd13ac1c8bb2831d1e15d30d55505ef2/themes/AllinOne/layouts/partials/staticman/form-comments.html#L30-L37
Is that caused by @staticmanlab?

@staticmanlab doesn't touch Akismet and Mailgun because his main goal is to show that Staticman's GitLab integration works, so that a truly open-source staticman commenting system is, in principle, feasible, for static sites hosted on Framagit, which is open-source.

Before the appearance of a free (as in both free beer and in freedom) alternative of Akismet and/or Mailgun, @staticmanlab won't try them.

@zxdawn2

This comment has been minimized.

Copy link

commented Aug 3, 2019

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Aug 3, 2019

However, mailgun has free account option. Why not support it?

  1. In this case, "free" as in "free beer" is offered, but not "free" as in "freedom" in GNU's norms.
  2. @staticmanlab's main goal is to test and demonstrate Staticman's native GitLab support, which had not yet been merged against the master branch, so I tried my best to minimise the setup and the corresponding git diff between the dev branch at 55d14306 and my deploy branch.
@zxdawn2

This comment has been minimized.

Copy link

commented Aug 17, 2019

@VincentTam Thank you for your help! I rebuilded the repository and got another problem:
The Comment content at the end of this page looks different from local (hugo server).

Local:
image

WEB:
image

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Aug 17, 2019

@VincentTam Thank you for your help! I rebuilded the repository and got another problem:
The Comment content at the end of this page looks different from local (hugo server).

Local:
image

WEB:
image

@zxdawn2

  1. The project is about the Node.JS app that converts HTML form data into GitHub/GitLab pull/merge requests. It shouldn't care whether you use GitHub/GitLab pages or not, as @eduardoboucas commented in #278 (comment). Your project is about the display of a HTML form, which has nothing to do with the structure of the form data, so perhaps you have to find a better place to ask, like Hugo Discourse.
  2. To ensure that your Staticman config is correct, a quick way to test is to use API clients like Postman, as @ntsim suggested in #219.
  3. Please be aware of the "503 Service Unavailable" error of the official production instance "api.staticman.net" in issue #307.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.