ProcessWire versioning

[marcin]

What about typical versioning of PW? (2.1, 2.2,...) I thought about module enabling autoupdate(do you think it would be complcated?), however, it would need some data to be compared(version, release date).

[ryan]

The structure is designed to support an auto update, so that this module can be written at some point in the future. The way it would work is that it would grab the latest zip (like from GitHub), then it would rename your /wire/ dir to /.wire.[version]/, and move the /wire/ dir from the zip into the location of the old one. At the same time, it would also replace the /index.php and /.htaccess files (unless you wanted to do that part manually). Lastly, it would run an update.php file from the zip to perform any necessary DB updates (if there were any).

On most servers, we can't assume that the /wire/ dir is writable, so it would likely unzip the latest PW version into a writable dir in /site/assets/, and then FTP into itself to rename and replace the /wire/ dir with the new one. I believe this is the same method that the Wordpress automatic update uses.

[Robert Zelník]

What about versioning of a particular templates or fields? Is it possible to set a template to store it's content changes?

Edit: In the meantime I found a mention in another thread that it is coming soon.

http://processwire.com/talk/index.php/topic,770.msg5921.html#msg5921

[ryan]

Versioning of templates or fields isn't currently planned, though page versioning will probably be enabled on a template (and possibly field basis). But that would be versioning page data, not template or field settings. Though if you want versioned template files, something like Git is always a good option too.

[Robert Zelník]

Oh, sorry, you are right, I meant page data.