How to register TVs in a package?

Hi there!
I tried to pack all of my migx-work in a package with the help of PackMan.
Worked fine.

But I wondered if there is any way to get the config-file - which I created here:
http://rtfm.modx.com/display/ADDON/MIGXdb.Manage+Events-Resources+in+a+CMP+with+help+of+MIGXdb#MIGXdb.ManageEvents-ResourcesinaCMPwithhelpofMIGXdb-RegistertheTVsforourprocessors%28getlist%2Cfields%29

- into the same directory as the rest of my component.
So how do I let migx know where to look, when I copy the file to /core/components/mycomponent/configs/mymigxconfig.config.inc.php ?

thanks,
janein

the path should be:


You should have the packagename defined in your MIGX-configuration
Than you can export your configuration with 'export to package'

After Installation of your package you can import this configuration into the MIGX-Configurator with 'import from package'
If don't want to import your config, you can use this exported json-file directly by adding the packagename to the configs-property
In TV-input-options:

configs: mymigxconfig:mycomponent

for the CMP-action, if you've created a CMP: &configs=mymigxconfig:mycomponent

hmm...
when I try to export my configs, I only get the .config.js but not the .config.inc.php
is there any chance to bring the information of "includeTVs" and "includeTVList" into the json file?

my guess into the blue: is this what the field "check resource tv" in the migxdb-settings tab is for?


strange thing is, that everything works fine on installation A (where I created it) but not on installation B (where I installed it as a package). TV-value are not saved there. Worked, when I had my config in the migx-directory. Did I miss a setting?
(parent resource and template are set to the correct values)

thanks,
janein

Use the Packman Directories Tab to include your component dir.

Export all your .js first. All config.inc.php will also be included as they are inside your directory. All TVs will be included automatically once you have a template with all of them associated and Added to the Package in the Templates Tab.

I suggest you to create a blank template (just don't use for nothing else than this) call it the same way of your package and associate all TVs you are using in your custom package.

Also, it makes sense to create a category for your CP, this way chunks, snippets, templates and tvs will be organized when deployed in another install.
Hope it helps. I've tested this a few times in different installs and works ok.

This is exactly what I did.
The confic.inc.php just doesn't work in the second install...

This should work. MIGX is installed correctly on your target-installation?

just reinstalled both, my package and migx. still doesn't work.

btw also the filtercombobox doesn't work on the second install. checked the TV and the snippet, both are there. (did this like in the tutorial for migxdb-eventsmanagement)

my config is in:



my package is called "myevents" and my migx-config is "myevents_events" (there are other configs with "myevents_" which work just fine)
my other "myevents_"-configs work fine, but they do not work with resources...

is it online accessible ?

no, sorry.
but here is my transport-package.
It's work in progress, so don't wonder^^
(required steps to make it work are in the readme)

great work!

I think to know your issue.
I removed the childresources-directory from migx-processor-directories.

Copy the directory
components/migx/processors/mgr/childresources/
from your working installation to your new installation into
components/migx/processors/mgr/childresources/
or into
components/myevents/processors/mgr/childresources/

Because this childresources-files was just thougt as an example how its possible to manage resources with MIGXdb i did remove them and want to create an extra example-package with them.

Will post some infos how you could simplify the installation-process later.