-
Notifications
You must be signed in to change notification settings - Fork 334
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.
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
SiteTree won't write new versions if only a field named 'Status' is changed #2455
Comments
How much time did you waste? |
kinglozzer
added a commit
to kinglozzer/silverstripe-cms
that referenced
this issue
Sep 11, 2024
8 tasks
PR: #3002 |
kinglozzer
added a commit
to kinglozzer/silverstripe-cms
that referenced
this issue
Sep 12, 2024
kinglozzer
added a commit
to kinglozzer/silverstripe-cms
that referenced
this issue
Sep 12, 2024
GuySartorelli
added a commit
that referenced
this issue
Sep 12, 2024
FIX: Remove legacy fields which prevent page publish (fixes #2455)
PR merged. This will be automatically tagged by GitHub Actions. |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please don’t ask how much time I wasted because of this bug 😭😂
Make changes to the value of status,
onAfterPublish()
won’t be called. The only time it’ll be called is if you also make a change to another field’s value as well. There are other issues this bug causes, but this is the easiest to reproduce.The cause is this line:
silverstripe-cms/code/Model/SiteTree.php
Line 1588 in 8a44071
I’m not sure if we should just remove that whole code block, but at the very least we should remove
Status
from the array as it’s no longer a field onSiteTree
(it hasn’t been since 2.4). We should also removeToDo
,VersionID
andSaveCount
.PRs
The text was updated successfully, but these errors were encountered: