[5.x]: Your changes could not be stored.
Open
Nobody has claimed this yet.
bug
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
Description
After doing the Craft CMS migration from 4 to 5, we're experiencing a lot of instances where trying to save an entry results in errors.
It starts with:
- A popup showing: "Your changes could not be stored." with the auto-save
- Looking in the console panel I see these errors; The Craft debug panel does not show any errors
- Saving the entry
Steps to reproduce
Upgrade Craft from 4 to 5.
Expected behavior
Would be nice if I can just resave the entry
Actual behavior
Unable to resave entries;
Craft CMS version
5.7.10
PHP version
8.4
Operating system and version
Linux 6.9.12
Database type and version
mysql 8.0.37
Image driver and version
GD 8.4.0
Installed plugins and versions
| Plugin | Version |
|---|---|
| Blitz | 5.11.4 |
| Blitz CloudFront Purger | 5.2.0 |
| CKEditor | 4.9.0 |
| Dashboard Begone | 3.0.0 |
| Elements Panel | 3.0.1 |
| Feed Me | 6.8.0 |
| Field Manager | 4.0.3 |
| Google Cloud Storage | 2.2.0 |
| Hyper | 2.2.6 |
| Imager X | 5.1.4 |
| Knock Knock | 3.0.3 |
| Navigation | 3.0.8 |
| Retour | 5.0.10 |
| SendGrid | 3.0.0 |
| SEOmatic | 5.1.15 |
| Sprig | 3.6.1 |
| Template Selector | 5.0.1 |
| Translations | 4.1.1 |
| Vite | 5.0.1 |
| Vizy | 3.0.9 |
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 Craft 4-to-5 upgrade on the reported PHP, MySQL, and Linux versions, then inspect the browser console and save request shown in the issue. Compare the failing save behavior with a resave attempt and identify a reproducible cause; done means upgraded entries can be saved successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100