-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
New behavior on latest versions: Unable to create new pages w/ git-gateway and gitlab #2383
Comments
I'm seeing the exact same behavior. I had just created a new site and started noticing this. However I do not have the |
@davidroberts63 did you use a starter or add the CMS to an existing site? Sent with GitHawk |
@erquhart I don't have |
I've added it to an existing site. It's 11ty. I've done it with two other sites in the past. The odd bit is that it can update an existing file just fine. Creating a new file is where the problem occurs. I've double checked that I'm not using an older cashed version. |
I'm trying to figure out which versions of netlify-cms + gatsby-plugin-netlify-cms work together properly. gatsby-plugin-netlify-cms@latest is also throwing an error for me :( gatsbyjs/gatsby#14794
I'm on the last legs of creating my 5th site with gatsby + netlify cms, and I've hit a stumbling block. Edit: I was able to bring back the CMS functionality by falling back to |
I'm having the same exact problem: Netlify: 2.9.2 Not using Gatsby nor netlify-lambda, using 11ty as the static site builder. My 11ty site was built with Eleventy CMS from the begining, and it always worked until this release. Config.yml doesn't set a editorial_workflow and is as follows:
Can't publish new content, the |
Tried resetting Gitlab token, to no avail. |
@unyo just a note, you should not be using |
Our project is in Hugo and is hosted on GitLab Backend Config:
Stack Trace:
|
Expected:
Able to create new pages via netlify-cms when using a gitlab repository and git-gateway as the backend
Actual:
Upon trying to create a new page, netlify-cms throws an error:
Applicable Versions:
"gatsby-plugin-netlify": "^2.0.17",
"gatsby-plugin-netlify-cms": "^4.0.2",
"netlify-cms": "^2.9.2",
"netlify-lambda": "^1.4.13",
CMS configuration
Additional context
On this line:
https://github.com/netlify/netlify-cms/blame/0ce995d78c8123a32a3e9ef7117fd5386f3cd02d/packages/netlify-cms-core/src/backend.js#L266
this.interface.unpublishedEntries
is always true since in git-gateway (below link) the function is always defined.https://github.com/netlify/netlify-cms/blob/master/packages/netlify-cms-backend-git-gateway/src/implementation.js#L416
this.backend
is either an instance ofGitHubBackend
orGitLabBackend
, depending on whether it's gitlab or github.https://github.com/netlify/netlify-cms/blob/master/packages/netlify-cms-backend-git-gateway/src/implementation.js#L416
Currently, only Github has a
unpublishedEntries
call:https://github.com/netlify/netlify-cms/blob/master/packages/netlify-cms-backend-github/src/implementation.js#L246
Whereas
unpublishedEntries
it is missing from Gitlab:https://github.com/netlify/netlify-cms/blob/master/packages/netlify-cms-backend-gitlab/src/implementation.js
And therefore when trying to create a new page, when trying to generateUniqueSlug, it'll fail with
this.backend.unpublishedEntry is not a function
since it doesn't exist in the instance of GitLabBackend.The text was updated successfully, but these errors were encountered: