Skip to content

EDITORIAL_WORKFLOW_ERROR: content is not under editorial workflow #7477

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.

Sign up for GitHub

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

Jump to bottom
Open
aaaaargZombies opened this issue May 24, 2025 · 0 comments
Open

EDITORIAL_WORKFLOW_ERROR: content is not under editorial workflow #7477

aaaaargZombies opened this issue May 24, 2025 · 0 comments
Labels
type: bug code to address defects in shipped code

Comments

@aaaaargZombies
Copy link

aaaaargZombies commented May 24, 2025 •
edited
Loading

Describe the bug

I keep getting this warning

Failed to load entry: EDITORIAL_WORKFLOW_ERROR: content is not under editorial workflow

And can't view unpublished content, though PRs / branches are created.

Likely related to this issue with very little detail #7025

To Reproduce

  • Error when saving a new entry
  • Unpublished entries not visible under either
    • workflows page
    • collection page

Expected behavior

Can create / view / edit unpublished entries

Screenshots

Error when accessing workflows page

Image

Branches and PRs have been created on repo

Image

On saving an new entry, redirects to "published" entry with no content

Image

Sometimes entries are show in collection list but with no content

Image

Applicable Versions: 3.6.3

<!doctype html>
<html>
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta name="robots" content="noindex" />
    <title>Content Manager</title>
  </head>
  <body>
    <!-- Include the script that builds the page and powers Decap CMS -->
    <script src="https://unpkg.com/decap-cms@^3.6.3/dist/decap-cms.js"></script>
  </body>
</html>

view code in context

CMS configuration

backend:
  name: github
  repo: breathe-easy-events/sheffield.breathe-easy.uk
  branch: main
site_url: https://sheffield.breathe-easy.uk
media_folder: "src/static/img"
public_folder: "/static/img"
publish_mode: editorial_workflow
collections:
  - label: "Home"
    name: "home"
    folder: "src"
    create: false
    fields:
      - { label: "Title", name: "title", widget: "string" }
      - { label: "Body", name: "body", widget: "markdown" }
  - label: "Pages"
    name: "pages"
    folder: "src/pages"
    create: true
    fields:
      - {
          label: "Title",
          name: "title",
          widget: "string",
          hint: "This will be converted to a slug eg. 'About Us' to 'about-us' which will be used in the URL",
        }
      - {
          label: "Menu item",
          name: "menu",
          widget: "boolean",
          default: false,
          hint: "Should this page be linked to from the navigation at the top of every page?",
        }
      - {
          label: "Discription",
          name: "discription",
          widget: "text",
          hint: "Metadata for previews on social media and search engines, aim for between 50 - 150 characters",
          pattern: ["^.{25,200}$", "Must be between 25 and 200 characters"],
          required: false,
        }
      - {
          label: "Social image",
          name: "socialImage",
          hint: "Image for previews on social media and search engines, should be 1200x630px, will be ignored if no alt text is provided",
          widget: "image",
          choose_url: false,
          required: false,
        }
      - {
          label: "Social image alt text",
          name: "socialImageAlt",
          widget: "text",
          hint: "Alt text describing preview image for screen readers",
          pattern: ["^.{25,}$", "Must be atleast 25 characters"],
          required: false,
        }
      - { label: "Body", name: "body", widget: "markdown" }

view code in context

Additional Context

This is a fork of a working installation. I am migrating from the main domain to a sub-domain. I am not sure if that should have any effect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug code to address defects in shipped code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aaaaargZombies