We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10327
    • 10 Posts
    Ive noticed many new additions in the package manager. Im getting alot of install errors that dont normally happen since I usually install a modx distro at least once a day.

    Usually starts out with a blank term agreement
    then, for example:

    ERROR:
    Could not install package with signature: subpages-0.1.0-alpha
    Wondering if its just because of the changes going on recently.

    Manual installs seem to work:
    (for those like me who aren’t super leet modx hax0rs)
     upload package to /core/packages/  and unzip your package.
    go to package manager and select ADD NEW PACKAGE and search LOCALLY. It should find your new addition and put it in your package management for install
      • 40045
      • 534 Posts
      Hi,

      yes, I’m in big trouble because of that^^...lost a day and have still no explanation for it^^...some packages like wayfinder work without problems...the strange thing is that I thought it may depends on the 2.0.8.pl (traditional) release, but I have a page on the same server with 2.0.8 that installs the same package (example copyright) flawless...I really don’t get it. I re-installed an absolutley clean copy (new folder, dbase, everything), didn’t change anything and jumped right to package management and tried to install some of the problem-packages, but the issue occured again...so a new installation didn’t help at all...


      That’s the error I’m getting when I try to install most packages:


      On the FTP everything looks ok, the zip IS unpacked (I did nothing manually...) and the manifest.php is there also, so I don’t understand where this error is coming from...



      I’ll try your "Manual Installation"-Tipp, but what should change??

      thx for any help!


      EDIT: OK, tried the manually install trick, didn’t work first. It was as I wrote, nothing changed...but I had a closer look on the error and the path had a 1.0.0-pl in it while the folder on the ftp only has a 1.0-pl, so a ".0" is missing and this was the problem in this case, I have to look further for the other packages...

      what I don’t understand is the cause of this problem, it is there since yesterday, before this was never a problem and I installed the same snippet (copyright) over 40 times^^... and it wasn’t updated or anything... installation just stopped working...wtf? =)

      EDIT2: OK, founda way around...when unpacking the zips, something messes up the foldernames, in most cases it’s enough to add a ".0" to the version name of the package (on the folder). The "Polls" snippet has another issue with the -rc1/-rc2 suffix, but if you pay attention to the folder name, you’ll get it =)...

      EDIT3 (2.3.2011): Redownloaded the 2.0.8 archive from modx.com, used it for a new installation and now magically it’s working again^^
        • 21738
        • 8 Posts
        This sounds similar to the problem I noticed yesterday, trying to update something using Package Manager. I think the "provider" is down (due to the new extras reshuffling?)...

        http://rest.modxcms.com/extras/ gives a 404 not found for me anyway, FWIW.
          • 17249 ☆ A M B ☆
          • 165 Posts
          Im getting the same kind of errors when trying to install some plugins, not all of them.
          I did a fresh install yesterday with 2.0.8-pl just to try this and it’s confirmed.

          Maybe its some kind of issue of 2.0.8-pl with older plugins.
          I’ve also found downloading some add-ons turns immediately the update field to Yes, which is weird. (The download button should bring it self the most recent version).
          When clicking in the Yes, then a small popup window appears with two radio buttons and no label for them.

          Got erros trying to install DocManager, SubPages, Polls and some others. Seems to be a generalized issue, but not to all of the plugins.
          [2011-02-28 19:28:46] (ERROR @ /connectors/workspace/packages-rest.php) Could not find package manifest at [[**MYROOT**]]/core/packages/docmanager-2.1.0-beta6/manifest.php
          [2011-02-28 19:28:46] (ERROR @ /connectors/workspace/packages-rest.php) Could not unpack package [[**MYROOT**]]/core/packages/docmanager-2.1.0-beta6.transport.zip to [[**MYROOT**]]/core/packages/. SIG: docmanager-2.1.0-beta6
          [2011-02-28 19:30:07] (ERROR @ /connectors/workspace/packages-rest.php) Could not unpack package [[**MYROOT**]]/core/packages/subpages-0.1.0-alpha.transport.zip to [[**MYROOT**]]/core/packages/. SIG: subpages-0.1.0-alpha
          [2011-02-28 19:30:10] (ERROR @ /connectors/workspace/packages.php) Could not unpack package [[**MYROOT**]]/core/packages/subpages-0.1.0-alpha.transport.zip to [[**MYROOT**]]/core/packages/. SIG: subpages-0.1.0-alpha
          [2011-02-28 19:30:10] (ERROR @ /connectors/workspace/packages.php) Could not unpack package [[**MYROOT**]]/core/packages/subpages-0.1.0-alpha.transport.zip to [[**MYROOT**]]/core/packages/. SIG: subpages-0.1.0-alpha
          


          Where should we file issues like this?


          Using Windows 2003 Server
          Revolution 2.0.8-pl
            • 40045
            • 534 Posts
            @lithiumlab

            got same issues with the "Updates" Links (for Snippets that have no updates it says "yes" and when I click it it says "no updates available" =)...I also noticed the emtpy licence fields and so on (like on your screenshots)
              • 21738
              • 8 Posts
              I don’t think it’s 2.08-pl (although I did notice it after donig the upgrade, but have confirmed behavior on hosts running older versions as well)... I think it’s the provider (http://rest.modxcms.com/extras/) is unavailable, and that causes some unpredictable behavior inside the package management script.

              Edit: in the other topic (http://modxcms.com/forums/index.php/topic,61691.msg350602/topicseen.html#msg350602), this was just listed as fixed. Thanks for the speedy response!
                • 17249 ☆ A M B ☆
                • 165 Posts
                Thinks it is a critical issue that needs to take action as soon as possible.
                It also adds a lot of friction to new users.
                The Package Manager should be aware if provider is down and do not allow to go further.
                Just passed yesterday like 3 hours trying to get a fresh install free of errors. sad


                Update: I’ll check the fix. Thanks a lot!
                Update: Fix is not working for me, even the update version shows up.