3 replies to this topic

[Robert Zelník]

When I create a new web site, I use two installations: a local (devel) site, where I test new changes, and a remote site, where I apply these changes when they work well. I would like to avoid duplicate work with creating fields and templates twice. Is there any intelligent way to clone these fields and templates between the local site and the remote site?

[apeisa]

No, not yet. Ryan has mentioned a method to export & import templates with fields using JSON. That would be great in many ways. Currently it is easy to export full site profiles, but that doesn't help in your scenario. Or other scenario where you want transfer certain templates from one site to an another (ie. you have build great product catalog on site X and want it to site Y also).

One way is to build module that creates all the required fields and templates, but I find it pretty cumbersome for that task.

Ryan: have you had time to look into this? I am available to help here, since this is very important stuff for our company. If you can share your initial thoughts on this, and I could try taking this further from there.

[ryan]

Import/Export with JSON strings (or web services or both) would be nice to have. It won't be very hard to do. I will try to work this into some future update for 2.3 or before.

[bpz]

Lol I came to ask the same question. We need migrations for processwire.
Ryan: can you publish the whole phpdoc API of PW's core so that we can build our own migrations?