decaporg / decap-cms

A Git-based CMS for Static Site Generators
https://decapcms.org
MIT License
17.92k stars 3.04k forks source link

Bitbucket on Save - Failed to persist entry: You must specify a provider and refresh token when calling netlify.refresh #3894

Closed mattortiz closed 4 years ago

mattortiz commented 4 years ago

Bug Description I've deployed a GatsbyJS site with the Netlify CMS at envyforge.com/admin. The Netlify CMS, in production, does load and we're able to view each of the collection entries defined in the admin/config.yml. However, on save of new or existing cms entries, we're getting the following error:

Failed to persist entry: You must specify a provider and refresh token when calling netlify.refresh.

As a note: all contributors have "write" access to the private repository. I am, however, able to save in local development using npx netlify-cms-proxy-server.

To Reproduce Steps to reproduce the behavior. For example:

  1. Request bitbucket access to my repo (as a comment here, along with your bitbucket email address). Note: I'll grant for those supporting and will provide relevant snippets inline here.
  2. Go to 'envyforge.com/admin'
  3. Click on 'blog' collection
  4. Create new blog entry (use the hint text if you have questions on what the fields are for)
  5. Click on 'Save'
  6. See error

Expected behavior Stable authentication and ability to save. It seems in looking up the error this may be an authentication token refresh issue.

Screenshots

Screen Shot 2020-06-14 at 5 37 29 PM

Applicable Versions:

CMS configuration backend: name: bitbucket repo: envyforge/envyforge.com branch: develop auth_type: implicit app_id:

local_backend: true publish_mode: editorial_workflow media_folder: static/images public_folder: src/data/images site_url: https://envyforge.com/contribute

collections:

Additional context Happy to provide any other context.

Thank you for your support!!

Matt

mattortiz commented 4 years ago

Seems to have cleared up. I'll re-open if it persists or recurs.

Thank you

erezrokah commented 4 years ago

See https://github.com/netlify/netlify-cms/issues/3779 And https://github.com/netlify/netlify-cms/pull/3847

A fix was merged, but no published yet