Silverstripe-Content-Blocks
Silverstripe-Content-Blocks copied to clipboard
Add Versioning
How about adding versioning of the blocks? Could be complicated with many_many and nested blocks though.
Hi @wernerkrauss - i must admit that versioning is quite low on my list. It's not something that i really require and it's complicated and will take time away from other stuff that i really wan't to have in this module. I'm not happy with the current state of the module, have a lot of changes planned but no time - to much work. I wan't to "tag" the module, so i can work on a new and improved version, do you have any info on how this is done? Do i just create a branch with some version number? and then keep working on master?
just create a tag for a commit, see http://git-scm.com/book/en/v2/Git-Basics-Tagging
e.g. git tag 0.0.1
which creates a version for packagist - nothing special or complicated ;)
ok thank you :-)
The easiest (but maybe a bit hacky) would be:
- create versions of blocks
- store an (recoursive) array of current blocks with versions in a hidden field of the Page.
We'd also need an "update all related pages" function when we have reused blocks.