We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 44196
    • 15 Posts
    When updating from 2.15 - 2.30. This message appeared in the toggle warnings section

    Error updating table for class modResource
    Array
    (
    [0] => 42000
    [1] => 1061
    [2] => Duplicate key name 'cache_refresh_idx'
    )
      • 3749
      • 24,544 Posts
      Warnings listed there are almost never important. Errors in red are the only thing to worry about.
        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
        • 44196
        • 15 Posts
        Thank you Bob. One last question after upgrading to 2.3.1 or somewhere along the stepping thru the upgrades. It seems my mail stopped working. I am using your Quick Email snippet and I get the following error.

        2014-11-04 03:52:53 SERVER -> CLIENT:
        2014-11-04 03:52:53 CLIENT -> SERVER: EHLO sitesensored.org
        2014-11-04 03:52:53 SERVER -> CLIENT:
        2014-11-04 03:52:53 SMTP ERROR: EHLO command failed:
        2014-11-04 03:52:53 SMTP NOTICE: EOF caught while checking if connected
        SMTP connect() failed.

        All settings are the exact same. And I can confirm it worked in 2.11.
        They only change I had to make was setting the date.timezone in the php.ini file in order to upgrade from 2.11 - 2.12

        Any Ideas?
          • 3749
          • 24,544 Posts
          Sorry, I can't explain that. I did test QuickEmail in 2.3 and it worked fine for me. Some of the early 2.1 branches are a little quirky and some suffer from cache corruption, so that might be it. It's common to have to clear the MODX cache and the browser cache and cookies after an upgrade before everything works.

          You should also check the SMTP System Settings to see if any of them reverted in an upgrade.

            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
            • 35756
            • 166 Posts
            profilneurotiker Reply #15, 9 years ago
            Hi there!

            I'm getting the same error as in bobbydigitals second post:

             [2015-04-17 16:22:41] (ERROR @ /modx/connectors/index.php) Error 42S22 executing statement: 
            Array
            (
                [0] => 42S22
                [1] => 1054
                [2] => Unknown column 'name' in 'order clause'
            )


            But it's within a freshly new install of MODx Revo 2.3.3. This error appears each time i'm editing and saving a resource, makes no difference if i do this with the admin account or the content editor account.

            I couldn't find a solution in this thread nor in another so far...anyone got a hint for this?
              • 3749
              • 24,544 Posts
              I've seen this before, though not on a fresh install. Somewhere around MODX 2.3.0, the modContext object got a 'name' field. MODX isn't finding that field, hence the error. The first thing to try is this:

              log out
              delete all files in the core/cache directory
              clear your browser cache and cookies (or use incognito or private mode)

              If that doesn't fix it, take a look at the database with PhpMyAdmin. Select the MODX db and check the modx_context table to see if it has a name field. If not, try re-running setup.

              If that doesn't fix it, you may have a missing or corrupted file in your MODX install. It's fairly common if you transfer the files individually with FTP.

              Last resort: Create the 'name' field yourself. It's:

              Type: varchar(255)
              Attributes (leave blank)
              Allow Null: Yes
              Default: NULL


              There is also an index on that field:

              Keyname: name
              Type: BTREE
              Unigue: No
              Packed: No
              Column: name
              Cardinality: 3
              Collation: A
              NULL: YES	





                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
                • 35756
                • 166 Posts
                profilneurotiker Reply #17, 9 years ago
                Thanks Bob again for your reply!

                I saw several other posts after I did this one that this issue seems to be related when using the VersionX-package...gonna wait for a moment if that really is what is producing the error, otherwise I'm gonna go the way you described...

                Merci beaucoup!