Answered Moving MIGX and all it contains to different installation

Hi Guys,

I have created multiple editors in MIGX wich i also need in a local installation, can i somehow transport from one installation to another? I see there is sort of an import/export function, i already exported something to a package, but i'm not sure of how to import it into the othe MIGX install.

Any ideas?

Cheers [ed. note: thapriest86 last edited this post 10 years, 6 months ago.]

There are two ways for exporting/importing MIGX-configurations

1. You can use the export/import - Button and copy the json-string to the export/import window of the other installation.

2. You can export to package -> Copy the exported files to the other installation into the same folder and run 'Import from package'

It is also possible to use the exported json-files directly without importing them into the grid.
You just need to specify the package with your query-parameters

&configs=configname:packagename

1. You can use the export/import - Button and copy the json-string to the export/import window of the other installation.
There's just nothing happening, no errors as well. (do i need to add something first?)

you really just need to create the configuration with the same name, save it and do export/import with the copied/pasted code and all configurations (tabs,columns and everything else) of that config should be imported

2. You can export to package -> Copy the exported files to the other installation into the same folder and run 'Import from package'
what would the syntax be?

Just click the Button 'Import from package' above the grid, add the name of the package into the modal and all configs found in that package-directory should be imported.
[ed. note: Bruno17 last edited this post 10 years, 6 months ago.]

Thank you Bruno, i thought it would import the whole thing so i did not create the configuration with name only first.

Cheers!

So I tryed the add to package option, no new files are created... How does this work?
I like to export 2o configs in one package and import those on another site.
Even better is that I could export the configs including all chunks needed.

Creating packages with snippets, chunks, templates, plugins of one or more categories and everything else, what is in your core/components/yourpackage-dir, is possible with
https://github.com/Bruno17/migxElementsManager

Quote from: Bruno17 at Feb 24, 2017, 02:52 PM

Creating packages with snippets, chunks, templates, plugins of one or more categories and everything else, what is in your core/components/yourpackage-dir, is possible with
https://github.com/Bruno17/migxElementsManager

And how do I put migx configs in there?

I tryed in modx CMP crate package and the add to package on each modx config... but that dit not work.

your package is allready created (core/components/yourpackage), right?
So, there is no need to create this package again with 'Create package' in the MIGX-CMP
This does only create a folder to start with under core/components/ ,does nothing else.

To export your configs into that components-folder, you have to fill the field 'package' in the MIGXdb - setting of each config. Then click 'Export to package' in each config.

This creates json-files under core/components/yourpackage/migxconfigs/