Request suggested debug methodology for "MISSING_CONFIG_BLOCK" error
See original GitHub issueFirstly, can I thank Alex and Eduardo for all the amazing work on Staticman. I can see Alex has spent an amazing amount of time helping people debug their builds, so thank you for that work and also if you have a donation link I’d be happy to buy you a coffee:-)
I’ve just built Staticman using Travis Down’s really thorough guide (and thanks to Travis as well!) at https://travisdowns.github.io/blog/2020/02/05/now-with-comments.html
I’m now live but have not yet registered for captcha so that’s still disabled in the config file.
On comment submission I’m getting an error:
success false
message "Error whilst parsing Staticman config file"
rawError
_smErrorCode "MISSING_CONFIG_BLOCK"
errorCode "MISSING_CONFIG_BLOCK"
Response headers:
Can you suggest the best approach to debugging this?
Also, is there any way for the comment system to work with no client-side javascript as this might make debugging a little easier?
Thanks again and all the best:-) Dug
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top GitHub Comments
@lrdj thank you for your kind words. I maintain this project in my free time so it’s always nice to hear positive feedback from users. @travisdowns is correct in his suggestions. The error handler fixes he references are indeed only in the dev branch at the moment, so I’d recommend deploying from that for now. If you switch to viewing the README on the dev branch, the deploy to Heroku button is smart and it’ll deploy the dev branch instead.
As far as making requests without JavaScript, you should be able to submit comments using a plain HTML form. See step 3 on this page for an example.
You can monitor #346 to see when these fixes are in master.
It seems the original issue here has been resolved so I’m going to close this issue. Feel free to continue to ask any follow up questions here and I’ll do my best to address them!