We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 20412
    • 1 Posts
    I’ve been trying to install plug ins such as TinyMCE & Ultimate Parent via Package Management on my local install of MODx Revolution. I’ve been able to download the zips using the Download Extras link and put them in the /core/packages/ folder manually but both times I’m still getting the same error no matter which way I do this.

    When I click Install I can click through the terms, readme and changelog (although all of these are completely blank, which is strange) but then am getting the following error when clicking Finish

    Console running...
    Attempting to install package with signature: tinymce-4.1.2-pl
    Package found...now preparing to install.
    Could not open file for reading: tinymce-4.1.2-pl.transport.zip?revolution_version=Revolution-2.0.7-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 tinymce-4.1.2-pl.transport.zip to C:/xampp/htdocs/lighthouse/sites/modx/core/packages/.
    Could not install package with signature: tinymce-4.1.2-pl


    I’ve been searching the forums and Google for these error messages and found most people pointing out that it’s most likely allow_url_fopen, cURL and/or fsockopen not being enabled but I’ve checked my PHP install and they are all enabled. I’ve also run a test on cURL to make sure that it works (I’ve used the other two on other local sites recently) and am getting no errors when attempting to use it.

    I thought it might be that PHP is unable to open the Zip file so have run a little test with the PHP Zip class - http://php.net/manual/en/book.zip.php - that also is working just fine.

    I also thought it might be some sort of permission error, even though working on a local install I didn’t think this would be the case, but MODx is already able to download and save the original zip to the plug ins folder so this can’t(?) be it.

    The problem seems similar to this thread - http://modxcms.com/forums/index.php?topic=51985.0 - as the errors are very similar but I’ve not been attempting any upgrades and haven’t messed with the core folder at all.

    Does anyone have any ideas as to what might be the problem here?

    If there’s any more info needed then please let me know

    -------------------------------------

    My system info:

    Web Server:

    • PHP 5.31
    • Apache (Local install via xampp)
    • Windows 7

    Database:

    • MySQL 5.1.41

    MODx:

    • Revolution 2.0.7
      • 22046
      • 1 Posts
      Hi,

      I have the exact same problem. Also with the empty form fields.
      And I just installed modx revolution 2.0.7
        • 29510
        • 2 Posts
        Hi, had a similar problem. Did you recently copy the modx folder to a new location?
        I had and saw that the error messages were all referring to the old installation folder.
        The other symptom was the license and other fields were always blank.

        I don’t have the exact steps to reproduce, but I tried to find every reference to the old folder and replace with the new that were left over (all were in the components folder) and flushing and clearing the cache.
          • 3749
          • 24,544 Posts
          Are you clicking on the "Download Extras" button in System -> Package Manager, then typing the name of the extra in the search box and clicking on the "Download" button in the grid at the right? That should automatically put the packages in the PM grid without you having to do anything manually.

          Be sure any prior versions of the packages have been completely removed and try deleting the files in the core/cache directory manually.
            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
            • 29510
            • 2 Posts
            Okay, I tracked down the cause of my error (remember I copied my install). Well I also copied the database. Turns out their is still a reference to the old install in the db.
            Table: modx_workspaces
            name: Default MODx workspace
              • 3749
              • 24,544 Posts
              Sorry, I always forget that one.

              I’m glad you found it.
                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