We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1582
    • 4 Posts
    I’ve just moved a site, I deployed an advanced install of 2.08-pl and moved the core out the document root, all went well until I tried to use the package management. Then I discovered in order to get it working I had to replace the new core/packages folder with the old core/packages folder uninstall and remove everything then install them like new again. However I’m getting errors for some of the packages:
    Wayfinder
    getResources
    tinyMCE

    For example Wayfinder’s output was:
    Attempting to install package with signature: wayfinder-2.3.0-pl
    Package found...now preparing to install.
    Could not open file for reading: wayfinder-2.3.0-pl.transport.zip?revolution_version=Revolution-2.0.8-pl
    MODx could not download the file. You must enable allow_url_fopen, cURL or fsockopen to use remote transport packaging.
    Could not transfer package wayfinder-2.3.0-pl.transport.zip to /var/www/html/core/packages/.
    Could not install package with signature: wayfinder-2.3.0-pl

    However I’ve managed to install:
    breadcrumbs
    getPage
    googlesitemap

    Why would some packages not work and others will? Anyone know how I fix it? Obviously the site isn’t working properly now because the site relied on the 3 plugins that won’t install, bit rubbish!

    Running a standard webserver and PHP safe mode is off. Fresh installs work, just this migration seems to be going a bit pair shaped sad

    cheers,
    Andrew

      • 3749
      • 24,544 Posts
      Make sure cURL is enabled and check the directory permissions on the new core/packages directory.
        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
        • 1582
        • 4 Posts
        curl is enabled. packages owner is apache, group is apache and permissions are 777. Still no luck sad
          • 3749
          • 24,544 Posts
          Try deleting all files in the core/cache directory and clearing your browser cache and cookies.

          If the host is using suPHP or suExec, the permissions need to be755 for directories and 644 for files.

          Otherwise, I’m out of ideas.
            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
            • 22303 MODX Staff
            • 10,725 Posts
            Yes, it’s the path value in the single row that exists in the modx_workspaces table — if you followed the instructions for moving an installation this would not be an issue.
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: Lucy at Apr 12, 2011, 10:53 AM
              Maybe the title could be changed to "Moving Your Site to a New Server or Directory" for dummies like me... rolleyes
              agreed, I’ll see what we can do... wink