1. I was using 2.0.1-pl and it worked great. Then I tried to test the MIGX-db, so I followed the tutorial:
When visit the Component>MIGX, the manager UI was so ugly that made me feel uncomfortable (need some css options for padding space).
Later I did upgrade MIGX to 2.2.0-pl and after that when I visited pages which were using template with migx-tvs, I got 500 error (which always make me feel doomed). The Component>MIGX page also produced 500 error.
After all I have to revert to 2.0.1-pl.
2. Fresh install core 2.2.4-pl and fresh MIGX 2.2.0-pl does have same problems.
3. Otherwises, I've meet some errors when visit packages management(I think it is not migx related but the core itself). At the time I upgraded core from 2.2.2 to 2.2.4 but the errors are the same
(ERROR @ /modx/connectors/workspace/packages.php) Could not transfer package archivist-1.2.3-pl.transport.zip to /home/x/htdocs/modx/core/packages/
...and many other pkgs
(ERROR @ /modx/connectors/workspace/packages.php) MODX could not download the file. You must enable allow_url_fopen, cURL or fsockopen to use remote transport packaging.
When I do the fresh core 2.2.4, this isn't replicated.
Well I think it's a real problem somewhere in the MIGX2.2.0-pl. I'm feeling really bad now because it takes me too much time to test and find out what is going wrong.
Is there someone else meet the same problems then?