Idea for module but zero knowledge writig one:s

[snowball]

Hope this is the right place to post...

I'm currently running a lot websites on CMS Made Simple and almost anything is possible and it always works out the way I want

I have a idea for a very nice module but no knowledge to write one...

The module I have in mind ads a very important feature to the backend of the website, ideal for editors and saves a lot of time, and more safety for mistakes while editing the content or html...

Wich steps to take to get this idea to reality?

Thanks

[uniqu3]

Describe your idea ask one of Developers and Sponsor one of developers?

[snowball]

Okay,

In the adminpanel, editing pages, news or html blocks it would be great to have a backup option field with a memory of 3 or 5 backups.

So what does it do?

While editing a page, html-block, code, scripts or any content on the website and you have nice results and everything works, you can press backup and the module makes a copy of the code and shows a icon eg. backup and timestamp. Every time you press backup the row moves and the fift get deleted as new ones keep coming.



In this case while you are working on the site and make some changes, test your page and suddenly there is a error in a item or some text or code missing... The only thing to do is press on one of the backup file's and press restore...

The module does a simple job , select all code en delete, next paste de code of the backup file and it's done.

Would add something to the workflow

[uniqu3]

In Terms of templates, ScriptDeploy was already doing part of this and in upcoming release it should do it even better.

But as mentioned if you would like a Version Control module, your best bet would be to contact some of developers if someone is interested to develop against a sponsorship, i assume it would be involved with allot of work so i don't think someone is willing to do it just for fun. but who knows.

[snowball]

It would be on every item in de whole backend, also for editing pages , news etc..

I have no commercial purpose with this idea, but gonna try figuring it out

Thanks for reply and feedback!

[Wishbone]

The issue is that each module directly access the database when updating their content, instead of using some sort of content API that writes data in a set way, like SilverStripe does, which has native version control, since everything extends the Content class.

News writes data differently than Pages and Stylesheets and Templates for example. Any module that would do this would require a 'pre-save' trigger for it to leverage and understand it's table structure and make a copy. What if a module upgrades and changes it's table structure? This would have to know it as well, or items would be dropped.

It sounds like the only way to have full (core and modules) version control is to have the core support it natively, and all modules would have to be compliant with it.