Wondering if others also think something like this would be useful. What if you could right click a folder of Resources > Download, and download a zip package that on a later import would re-create those resources.
Something like this could be useful when dealing with content migrations of large websites where, by the time you finish something on development a group of resources has already been updated.
jpdevries
-
☆ A M B ☆
- 2,475 Posts
I really like that idea. Nice UX.
With Vapor, this should be pretty straight-forward, this would require that you also download the templates (because each resource is assigned to one), the TVs, probably you'd need the Chunks and Snippets too, and probably the resource groups.
Or, you could just do a simple dump and grab only the page content... but you might lose TVs if you did that.
Bob's myComponent can export resources and also its templates and build transport-packages of them.
It will get easy to select which Resources to export with the myComponentMigxUi:
http://www.revo222.webcmsolutions.de/index.php?id=51
For me this would definitely be helpful! For example I have custom help / documentation system (which replaces the modx built in one) which would be much easier to export with a feature like that (and yes, I confess, still didn't try mycomponent^^...and in the same sentence, looking forward for that mycomponent migx ui! =D)
I've never actually tested it, but MyComponent has an API (completely undocumented). You would still need a small config file, but you can send everything you need in the $scriptProperties array and call the individual methods to export objects to the build files and create the necessary resolvers, then run the build snippet.
