Closed robbieaverill closed 5 years ago
There has been plenty of discussion in silverstripe-versioned
about this issue: https://github.com/silverstripe/silverstripe-versioned/issues/195
I think it's probably fair to close this as a duplicate of that issue? You could possibly argue that you should be allowed to create a published version of a page at any time so the timestamp is atleast captured for showing history related to that timestamp. Perhaps that'd be an issue on CMS though if it's not currently possible?
Yeah this particular issue I think is happening because when you click Save on the page, it doesn't detect any new changes so doesn't write a new version (default behaviour).
Projects implementing elemental and wanting to disable this could probably create an extension for the CMS controller and adjust the save logic to force a new version.
Otherwise this would be resolved by fixing that issue, yeah
Version: SS 4.3.x-dev and elemental 3.2.x-dev
Expected: there should be two Published versions of the page listed
Actual: there is only the initial Published version of the page listed
I suspect this is a manifestation of #527 and #528