-
Notifications
You must be signed in to change notification settings - Fork 3
Staticman v2 error: Too many requests in this time frame #373
Comments
Thanks for the great comment! I will sit down and give this a look. |
I've just published a pre-release of my fork of Beautiful Hugo and built an demo site on GitLab, thanks to your great tutorial. |
Ugh...I am finally getting around to reviewing this code and your pull request on Beautiful Hugo. You have done some great stuff. I am going to work on integrating it into my setup over the next few days. I put Staticman into my blog before someone built it into Beautiful Hugo and just never circled back. I am glad you found my blog useful. I know very little about forms and was learning Go templating on the fly, so thanks for taking my madness and making it clean! |
Looking back, the code for the reply target anchor in a comment reply can be much simpler if the id attribute for the article tag which wraps the comment is set to be the comment id in the YML file. This makes the link of a post comment much more stable than the current approach ( |
This reminds me eduardoboucas/staticman#222 and eduardoboucas/staticman#227. I suspect that the public production instance of Staticman v2 is hosted on a paid Heroku dyno and that the server is hitting the limits of his Heroku billing plan.
Here's the comment that I intend to leave under your great post about nested Staticman comments.
Test reply to Dan.
I think the "In reply to
<name>
" contains a logic error. When the "reply to thread button is clicked, thechangeValue
function only setsreply_to
to_id
of the head of the thread, and theparentName
is tied withparentId
. In one single thread, there's only one head (i.e.parentId
), but it may have multiple participants (i.e.parentName
).Nonetheless, I've learnt a lot from your explanations. Thanks for this great article!
The text was updated successfully, but these errors were encountered: