Answered Not loading MIGX after upgrading in 2.4.0

Maybe smbdy have the same problem after upgrading Revo?



http://stackoverflow.com/questions/32106342/migx-tv-not-working-on-modx-revolution-2-4-0

Occasionally on some upgrades I've found it necessary to uninstall MIGX and install it again. Nothing consistent, though, and this last upgrade to 2.4.0 didn't seem to have any problem with it on any of my sites.

I am having the same problem. MIGX works on my development server with Modx version 2.4 but not on my production server, which is on a shared hosting site.

I get the same screen as @itcraft. When I close the box I found that the Error box had been triggered - but it was completely transparent. ( It is only visible when you try and drag it. ) I changed my Debug setting to -1 but still don't get any error messages.

The problem is only on MIGXdb - the TV's work properly.

Check the host's PHP version. MODX 2.4.0 requires PHP 5.3.3, or above.

I usually find that I have to uninstall and reinstall MIGX after an upgrade. I don't know why.

The hosted site is running PHP 5.5.29 and my development site is running PHP 5.5.9-1ubuntu4.11. The only different that jumps out is they are running different JSON versions. The hosted site runs 1.2.1 and I have 1.3.2 with the JSON-C bundle. And, reinstalling MIGX didn't help.

The other big difference between the hosted site and the development server is the location on the core files. On the hosted site they are not in the document tree.

I put in some error logging code show which sections of the code is being run. It looks like migx > processors > mgr > defaults > fields.php is not being run.

I still need to track down where that is loaded from.

is there a chance to have a look into the manager for me?
Then PM me.

I tracked down my problem to a section of the query string. The the 'object_id' is set twice, first in the base of the query string and also as a JSON encoded object in the 'storeParams'.

http://www.mysitename.ca/assets/components/migx/connector.php?action=mgr%2Fmigxdb%2Ffields&tv_id=1&tv_name=&class_key=modDocument&wctx=mgr&object_id=3&configs=amazoncodes&resource_id=&co_id=&isnew=0&isduplicate=0&tempParams=&storeParams=%7B%22action%22%3A%22mgr%2Fmigxdb%2FgetList%22%2C%22configs%22%3A%22amazoncodes%22%2C%22reqTempParams%22%3A%22%22%2C%22reqConfigs%22%3A%22amazoncodes%22%2C%22resource_id%22%3A%22%22%2C%22object_id%22%3A%22%22%2C%22 . . .

I think one of the mod_sec rules from the hosting service is causing the problem. As a 'work around', I remove the 'storeParams: storeParams,' line (line 209) from templates > mgr > grid > default.grid.tpl - which worked - but may have introduced other problems.

The site is hosted on HostPapa and I can't say for sure I ever had MIGXdb working on that server. MIGtv was working and seems unaffected by any of the changes I made.

Hope this helps.

UPDATE -
The problem was the Apache mod_sec module. HostPapa turned off the rules that were affecting the query string and that fixed the problem.

Great! I'm glad, you got the issue sorted!