— test — 1 min read
There are a couple of issues that users face while integrating or working with Netlify CMS and while the community is doing their best fixing them, here is a list of known issues and their solutions.
A list of error messages and their possible cause(s) to provide more context while debugging.
1API_ERROR: {"message":"404 File Not Found"}
src/posts
for example).1API_ERROR: Not Found
1API_ERROR: Not Found
1Failed to load settings from /.netlify/identity
If you’ve invited some users and opened the invitation link from the generated emails but as they try to log in they get the following error message:
1Email not confirmed
<head>
. The upside of this method is that it’s fast and easy, no other configuration needed. The downside is that all of your users are downloading the widget while they might not need it. That’s kb’s wasted. Unless you’re using Netlify Identity for something else than the authentication of CMS users, utilize the next solution.admin/
page, so you might as well have your users confirm their email there. Learn how to update your invitation emails here.Credits to @tomrutgers. Check here for more details.
If you deployed Netlify CMS to Netlify using a template and didn't receive an invitation email after deploying the site, check your email settings to make sure that your email provider doesn't block emails from no-reply@netlify.com.
To make Netlify CMS responsive for usage on mobile, here is a temporary CSS solution to include to your admin/index.html
below your closing </body>
tag so it can overwrite netlify-generated css.
Credits to truongoi.