We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1841
    • 141 Posts
    Hi,

    I've been trying to upgrade from Modx Revo 2.25 to 2.27 and every time I go through the setup process I get the same error messages:

    Error updating table for class modTemplateVarResource
    Array
    (
    [0] => 42000
    [1] => 1061
    [2] => Duplicate key name 'tv_cnt'
    )
    
    Error updating table for class modResource
    Array
    (
    [0] => 42000
    [1] => 1061
    [2] => Duplicate key name 'cache_refresh_idx'
    )
    
    The install failed because MODX could not unpack the <<site-path>>/core/packages/core.transport.zip package. Make sure that the <<site-path>>/core/packages/core.transport.zip file exists and is writable, and that you have made the <<site-path>>/core/packages/ directory writable.


    It's really strange as I set the Permissions on the relevant folders / files to 777 just to get this working and STILL get the error!

    For some reason the tick-box on the previous set up screen (Core Package has been manually unpacked) is untickable. I've managed to upgrade on a Linux shared server ok, but on my main site I can't get it to work at all.

    The main site is running on an NGINX server with PHP 5.3.16 & Mysql 5.5.27. Up to REvo 2.25 I've not had an issue and been using this server for quite some time, couldn't upgrade to 2.26 and just thought it was an isolated issue with that version but still can't with 2.27 - any ideas anyone?
      • 22840
      • 1,572 Posts
      Try using 755 on the referenced files, as far as im aware NGINX folder permissions should be 755
        • 1841
        • 141 Posts
        Permissions are set by the OS rather than the web server software, setting to 755 won't even let me get as far as I did - setup says folder not writeable.

        Thanks for input though
          • 22303 MODX Staff
          • 10,725 Posts
          Those are just warnings telling you that those specific upgrade steps have already been run before on your database. These are not errors in themselves.
            • 1841
            • 141 Posts
            Yes it was more the install failed issue rather than the warnings that I was concerned about, must be some sort of persmissions issue
              • 27708 MODX Staff
              • 2,502 Posts
              How did you upload the files to do the Upgrade? FTP always has the potential for transfer failures and incomplete files. It's always good to reupload and re-run setup, especially if you have a working site.
                Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                • 1841
                • 141 Posts
                Hi Jay,

                Yes it was via FTP however I've tried re-uploaded and re-run a few times with no success.