An image upload field on a dataobject with no versioning. Uploading an image, and pressing ‘apply changes’ leaves the unpublished message on the image. Refreshing the page shows that the image is actually published


nvm, it looks like it’s a bug in the UI. It still shows draft over the image after pressing ‘apply changes’. You need to refresh the page to see that the image is published


Has there been a recent change with $owns and dataobjects that don’t have the versioning extension? I’m sure that my images were being published on those dataobjects, but it seems like that’s not the case now?


@Wilson S this is top of my head info though, please don't be afraid to assert facts :)


Any ss core peeps willing to give a steer on https://github.com/silverstripe/silverstripe-framework/pull/9236? Thanks

Show 1 attachment(s)
Update ReadOnlyTransaction test to correctly fail and use the rollback by michalkleiner · Pull Request #9236 · silverstripe/silverstripe-framework

Disclaimer The test is deprecated since 4.3.0, but still left in the suit. Problem Test failing for SQLite database. I couldn't figure out why would the rollback event be triggered in the catch...

Hide attachment content

ASSETS_PATH is a constant, not an environment variable, afaik @Wilson S