craftcms / craftcms/cms

"draft not found" error when saving an entry

Open
#9,898 14 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

Description

Our client has twice encountered this issue, though we do not know the exact steps to reproduce. This may be related to issue #9868...

Our client has an entry (in a Structure section fwiw) and can click to edit it; however when she clicks save, the error "Draft not found" is displayed. If I log in as a different user, I am able to save the entry fine.

The client's entry has a mix of blue and yellow field markings, signifying there are changes to her draft and also changes to the underlying published version. I do not know if this is related to the underlying cause.

The workaround we have established is that the client must click "Create a draft", and then "Apply draft".

I can supply a DB backup.

Additional info
  • Craft version: 3.7.13
  • PHP version: 7.4.23
  • Database driver & version: MySQL 5.5.5
  • Plugins & versions:
    • Agnostic Fetch 2.0.4
    • AsyncQueue 2.3.0
    • CP Field Inspect 1.2.5
    • Imager X v3.5.2
    • Knock Knock 1.2.16
    • Postmark 2.1.0
    • Redactor 2.8.8
    • Redactor Custom Styles 3.0.4
    • SEO 3.4.13
    • Typed link field 1.0.25
    • Vite 1.0.16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reviewing related issue #9868 and reproducing entry saves with mixed blue and yellow field markings, comparing the affected client with another user; use the offered database backup if available. Done means the affected entry saves without the Create a draft/Apply draft workaround and the cause is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, php
Domain
backend, content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.