1.8.1 - Cannot publish new documents

[Jinksi]

- Do you want to request a feature or report a bug?

Bug

- What is the current behavior?

Using CMS version 1.8.1, cannot publish new documents. Get Failed to persist entry error.

See console.log screenshot:

May have something to do with

- If the current behavior is a bug, please provide the steps to reproduce.

Creating a new document in a collection, clicking Publish Now

- What is the expected behavior?

Rolling back to 1.8.0 fixes this issue.

- Please mention your versions where applicable.

Netlify CMS version: 1.8.1
Browser version: Chrome 67

Node.JS version:
Operating System: macOS 10.13.3

- Please link or paste your config.yml below if applicable.

[Jinksi]

FYI using git-gateway

[erquhart]

Unable to reproduce so far. Can you still reproduce? Any error message toast notifications popping up when it fails?

#1239 seems the only likely PR in 1.8.1 to cause something like this, but it should have produced a toast notification if that was the case.

[Jinksi]

Yes, toast notification is:

Failed to persist entry: API_ERROR: Not Found

[erquhart]

Can you link to a repo that reproduces? Still not able to trigger the error.

[Jinksi]

https://github.com/Jinksi/test2

CMS new post page
I've opened invites if you want to log in.

I've used the one-click-hugo-cms template and added this commit to use 1.8.1.

I'm able to update existing posts, but cannot create new posts.

[kyleoliveiro]

I'm trying to get started with Netlify CMS, and I'm running into this error as well while using github backend.

Edit: Just tried downgrading to 1.8.0. After doing so, I am able to publish posts.

[satzz]

Also happening to mine(It didn't a few days ago). I'm using unpkg.com/netlify-cms@^1.0.0. The error happens when saving a new entry in editorial workflow, as well as when publishing.

[erquhart]

Working on this now.

[erquhart]

Fixed in 1.8.2. Can someone confirm and close?

[papandreou]

Was the new version published to npm? I don't see it:

$ npm info --json netlify-cms | jq -r '.["dist-tags"].latest'
1.8.1

The npm guys had an incident the other day that caused published packages to not be available immediately, could be that the problem is back: https://status.npmjs.org/incidents/3rjzvts6v98k

[tech4him1]

It is live on npmjs.com and unpkg.

[papandreou]

Ah, there is a new incident reported: https://status.npmjs.org/incidents/238t55n6f03f

[erquhart]

Whoops, accidental close.

I'm seeing it on unpkg now.

[papandreou]

Confirmed fixed (via unpkg)

[papandreou]

I wrote an email about the missing package to npm support.

[erquhart]

Awesome, thanks @papandreou.

[papandreou]

They wrote me back, and it's there now 🎉

[Jinksi]

All working 👏