We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37012
    • 32 Posts
    After migrating my site from the production to local, everything seems to work except package manager. It simply does not load the package list. If I go to package browser, I can see some of them are already downloaded as they don't have the download button.

    Is there a way to uninstall the package without manager?
    • Yes: you can uninstall packages manually, but it may be laborious by hand. In general, files live inside core/components/<package_name> and assets/components<package_name> but many packages also install bits into the database, and those can be hard to track down without the "receipt".

      It can be hard to switch environments -- I've found the local environment can be touchy, especially when it comes to managing anything that requires internet connectivity (e.g. the RSS feeds can fail spectacularly if you turn off your connection), so I imagine something simple like that could affect the package manager too.
        • 37012
        • 32 Posts
        The environment itself should be alright, as before in the same place I had the original local environment which worked.

        I tried clearing the cache, flushing privileges and other stuff, but it won't load still.
        • Desktop environments are the hardest to work with in my experience: because you're doing all your day-to-day stuff on them, they are much more volatile than a normal web server dedicated to a single task. As always, check the logs and see what they're telling you.

          You can try a couple utils here:
          https://github.com/craftsmancoding/modx_utils

          Namely, the test_config.php and modx_ready.php -- they may not turn up anything, but at least you check the simpler things.
            • 37012
            • 32 Posts
            I've checked your utils, but they say everything is fine.

            [2013-06-19 16:00:28] (ERROR @ /modx/connectors/workspace/packages.php) Could not open file for reading: formit-2.1.2-pl.transport.zip?revolution_version=Revolution-2.2.6-pl
            [2013-06-19 16:00:28] (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.
            [2013-06-19 16:00:28] (ERROR @ /modx/connectors/workspace/packages.php) Could not transfer package formit-2.1.2-pl.transport.zip to C:/wamp/www/modx/core/packages/.

            I was getting this in error log, but I found a way to put the formit package where it was required. Now, I get nothing in the log when I refresh, and it still does not load.
              • 3749
              • 24,544 Posts
              Check the path in the modx_workspaces table in the DB.
                Did I help you? Buy me a beer
                Get my Book: MODX:The Official Guide
                MODX info for everyone: http://bobsguides.com/modx.html
                My MODX Extras
                Bob's Guides is now hosted at A2 MODX Hosting
                • 37012
                • 32 Posts

                That path I set too, as in documentation. When I press Refresh, it seems to load infinitelly.
                • Firebug showing any errors from the Ajax requests? Do you have PHP error reporting set to all the way on so you can see errors, notices, and warnings?
                  • Did you use Vapor to migrate an package of the site from one server to the other? If so, I've had Package Management hang because the package Vapor created was huge. Deleting it manually helped bring the Package Manager back.
                      • 37012
                      • 32 Posts
                      Thanks everyone for comments and suggestions.

                      I did not use Vapor - just simple zip and Dump as in the docs. I transfered sites multiple times, so I know this process very well.

                      So, the PHP errors were on, but there is something in the PHP error log:
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP Notice: unserialize(): Error at offset 2627 of 6399 bytes in C:\\wamp\\www\\modx\\core\\xpdo\\om\\xpdoobject.class.php on line 1049, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP Stack trace:, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 1. {main}() C:\\wamp\\www\\modx\\connectors\\workspace\\packages.php:0, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 2. modConnectorRequest->handleRequest() C:\\wamp\\www\\modx\\connectors\\workspace\\packages.php:3, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 3. modConnectorRequest->prepareResponse() C:\\wamp\\www\\modx\\core\\model\\modx\\modconnectorrequest.class.php:66, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 4. modConnectorResponse->outputContent() C:\\wamp\\www\\modx\\core\\model\\modx\\modconnectorrequest.class.php:79, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 5. modX->runProcessor() C:\\wamp\\www\\modx\\core\\model\\modx\\modconnectorresponse.class.php:131, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 6. modProcessor->run() C:\\wamp\\www\\modx\\core\\model\\modx\\modx.class.php:1599, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 7. modObjectGetListProcessor->process() C:\\wamp\\www\\modx\\core\\model\\modx\\modprocessor.class.php:173, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 8. modObjectGetListProcessor->iterate() C:\\wamp\\www\\modx\\core\\model\\modx\\modprocessor.class.php:477, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 9. modPackageGetListProcessor->prepareRow() C:\\wamp\\www\\modx\\core\\model\\modx\\modprocessor.class.php:502, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 10. xPDOObject->toArray() C:\\wamp\\www\\modx\\core\\model\\modx\\processors\\workspace\\packages\\getlist.class.php:78, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 11. xPDOObject->get() C:\\wamp\\www\\modx\\core\\xpdo\\om\\xpdoobject.class.php:1916, referer: http://win2k8r2:8080/modx/manager/?a=69
                      [Thu Jun 20 10:15:58 2013] [error] [client 192.168.1.64] PHP 12. unserialize() C:\\wamp\\www\\modx\\core\\xpdo\\om\\xpdoobject.class.php:1049, referer: http://win2k8r2:8080/modx/manager/?a=69

                      a=69 is the problematic page.

                      Also, I do get the error in firebug:

                      SyntaxError: syntax error
                      (<br />

                      ext-all.js (line 7, col 1)

                      and that line is probably too long to post here.