minimal-mistakes: Staticman no longer allows comments
Environment
- Minimal Mistakes version: 4.16.3
- Ruby gem or remote theme version: n/a
- Jekyll version: n/a
- Git repository URL: justinrummel/jr.com-mm
- GitHub Pages hosted (if yes provide URL to site): No
- Operating system: n/a
Expected behavior
Currently not able to post comments.
Steps to reproduce the behavior
It appears that Staticman is enforcing CORS, and current MM sites that use Staticman can no longer post comments. Confirmed this is also impacting your own site.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (16 by maintainers)
Seems like the best approach these days is to fork the Staticman repo and spin up your own instance on a free Heroku plan.
Closing as there’s nothing the theme can do about improving the reliability of the public endpoint.
Thanks @VincentTam
I’ll take a look at your blog post again and try to follow the directions. If there are spots that I feel are unclear I’ll reach out to you.
@deadlydog I don’t have any plans to change how Staticman is enabled in the theme. With all it’s issues the last year I’m not really motivated to until it stabilizes.
Even the new v3 GitHub application endpoint is having it’s issues. Calling it out as an official comment solution for the theme has only brought more attention to it and put me in a support role for when it goes bad.