[5.x]: incorrectly shows red warning sign after save draft (in conjunction with the workflow plugin)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
Description
We have observed the following behavior:
In one of our projects, we are utilizing the Workflow plugin. A project user creates a new draft, incorporates their changes into an entry, and subsequently submits these changes for review. The draft is saved correctly; however, Craft then displays a warning indicating that the draft could not be saved. From a functional standpoint, everything appears to be working correctly; however, in terms of usability, this is confusing and suboptimal for the user. We suspect this issue lies with Craft itself, rather than with the plugin.
Thank you for looking into this!
Steps to reproduce
- Open an entry
- Create Draft
- Change something
- save draft / Send workflow review request
Expected behavior
no red warning sign, just show the green checkmark
Actual behavior
show green checkmark, after some seconds (and in our opinion after a js request) - the red warning sign be shown -> see screenshot above
Craft CMS version
5.10.2
PHP version
8.2.26
Operating system and version
linux
Database type and version
PostgreSQL 16.14
Image driver and version
Imagick 3.7.0
Installed plugins and versions
-Workflow v3.0.16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the draft-save and workflow review steps on Craft 5.10.2 with Workflow 3.0.16, PHP 8.2.26, and PostgreSQL 16.14. Compare the successful save indication with the later JavaScript request that causes the red warning. Done means the workflow submission still succeeds and only the green checkmark remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100