migx xml schema lost?

I have 2 custom tables, used migx to create packages for each of them and created 2 cmp's to manage them.

The cmp's are working just fine, also pulling content from the packages still works.

However, in the migx management under the migx tabs where those packages used to be listed, they're gone.

If I try to load the schema, the textarea remains empty as well.

Now I need to add a third table, third package and third cmp. However,.... I'm afraid if I create it the former to packages may disappear since the xml schema field is empty right now but I´m sure it must still be somewhere since the packages are still accessible.

Question is twofold.
1st. What made my first 2 packages disappear from the overview, leave my schema field blank and how do I get it back in case I need to make amendments?
2nd. Is my fear of losing the first 2 packages if I add a third legit? Or is there something I'm unaware of that would prevent that nightmare from happening?

Can you check, if the xml-file is there under core/components/yourpackage/model/schema ?

when you talk from 'packages', do you mean your MIGX - configurations?

And if the CMPs still are working, the configurations are still there, for sure.
Otherwise the CMPs wouldn't work any more.

Quote from: Bruno17 at Oct 06, 2015, 08:19 AM

Can you check, if the xml-file is there under core/components/yourpackage/model/schema ?

when you talk from 'packages', do you mean your MIGX - configurations?

And if the CMPs still are working, the configurations are still there, for sure.
Otherwise the CMPs wouldn't work any more.

Hi Bruno

Yes, the configurations are still physically there in their core/components folders. So i could just back them up and see what happens if I add a new configuration (yeah, thats probably what I meant by packages).

But I'd really like to re-add them to the migx configuration screen again so I can make amendments if need be the usual way (usual way meaning I merely create the needed tables and have migx take care of writing the configurations).

Would copying the contents of the xml files into the appropriate textarea of the migx screen suffice to do that?

Also. What could have caused this?

Edit: I added a new configuration for an external table using migx. The files have been written to the core/component/ folder. But it isn't listed in the modx configurations overview.

Now, if I click 'add item' the following appears:



Any thoughts? [ed. note: Towila last edited this post 11 years ago.]

I have no idea, why they aren't there anymore. Never have seen that issue. They shouldn't go away from alone.
You can import them within the MIGX - cmp.
There is a button 'Import from Package'

When you want to use the configs from db then, and not the files-configs,
make sure, you have not &configs=yourconfig:yourpackage in the CMP-menues, but just &configs=yourconfig

this are just Notices, they are shown ,depending on php-settings.
Which MIGX-version are you working with?

Quote from: Bruno17 at Oct 07, 2015, 08:14 AM

I have no idea, why they aren't there anymore. Never have seen that issue. They shouldn't go away from alone.
You can import them within the MIGX - cmp.
There is a button 'Import from Package'

Ah, okay. Haven't noticed that one before. Unfortunately, if I enter the correct package name the ajax loader shows up and doesn't dissappear. Probably more notices beings sent out. Will have to check.

When you want to use the configs from db then,
make sure, you have not &configs=yourconfig:yourpackage in the CMP-menues, but just &configs=yourconfig

try to set the system-setting 'debug' to 0

but I think, all or most notices should be fixed in the meanwhile, if you have an older version of MIGX

Quote from: Bruno17 at Oct 07, 2015, 08:18 AM

this are just Notices, they are shown ,depending on php-settings.
Which MIGX-version are you working with?

Hmmzzz. Didn't think about updating yet. It's 2.8.1-pl. Going to update now.

And this is what happens if I click migx now after a succesful? update



This sort of crap always seems to happen after updates of either modx itself or one if its components.

Great, another wasted few days to get everything back to working order again. Fuck it, Im done with modx. Period.