-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Error creating collection entry depending on title value #1121
Comments
Would it be possible to link your repo, so that we can try to reproduce? |
Yeah of course, the repo is at https://github.com/ianmilliken/mpc. It's worth me mentioning that the problem doesn't occur on when running on localhost |
Are you using |
I'm using the |
That might explain why it's only working locally :). Can you try using |
Yep I've tried |
Forked and was able to repro. Digging in. P.S. fantastic work on this site @ianmilliken, bravo. |
Cheers @erquhart, thanks for looking into it. |
Just now getting around to actually looking into this - it's because you're using http instead of https, which shouldn't be possible. It's covered under #1141, going to close this in favor of that. It seems Netlify Identity invite links are sending folks to the insecure url. Until there's a fix, just manually ensure that you're connecting via https. |
- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
On production, I'm creating an entry in an already populated collection called 'Services'. Depending solely on the title of the entry, NetlifyCMS fails to create it and returns an error.
- If the current behaviour is a bug, please provide the steps to reproduce.
- What is the expected behavior?
The entry should be created, and would be if the name were anything else it seems
- Please mention your CMS, node.js, and operating system version.
- Please link or paste your
config.yml
below if applicable.I know this is ultra specific, so I'm not expecting any definitive answers, but if anybody has an idea about what might be causing this or has experienced something similar then it'd be great to hear from you.
The text was updated successfully, but these errors were encountered: