We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36582
    • 463 Posts
    Thanks for the help and advice. I have managed to upgrade to 2.2.15 (from 2.2.14) without any problems. It's a pity about 2.3 but at least I should be secure.
      Web site design in Nottingham UK by Chris Fickling http://www.chrisficklingdesign.co.uk
      • 36582
      • 463 Posts
      Well I'm nearly there!

      Manager is hanging when going to System Settings->Core->Back-end Manager.

      Console is showing the following error:

      TypeError: 'undefined' is not a constructor (evaluating 'new b[d.xtype||e](d)')

      in: ext-all.js

      Any help?
        Web site design in Nottingham UK by Chris Fickling http://www.chrisficklingdesign.co.uk
        • 15877
        • 55 Posts
        Having the menu disappearing too.
        MODx 2.3.3 on local Wamp manager and on a remote Apache server.

        It seems to be linked to the database I am using for this website.
        When I reload it, the menu displays fine.

        No errors in the FF console.

        Emptying the cache and removing JS and CSS compression did nothing. [ed. note: kilroy last edited this post 11 years, 7 months ago.]
          • 37514
          • 178 Posts
          Hi there,

          We were struggling with this. Our tech / dev ops person reports:

          The issue was not with load, php, compression. The issue occurs because "eval var=$userNav” doesn’t result in the menu being generated. I think this may be due to an older version of core-transport being in place when the update process runs.

          Upgrade to 2.3.3-pl fixed this when I deleted the old version forced it to unpack core transport. The steps were:

          1) Make sure core/packages/core.transport.zip is from the ModX version that you are upgrading to
          2) remove existing core/packages/core
          3) Set setup/config.xml to use "<unpacked>0</unpacked>”
          4) run "php ./index.php --installmode=upgrade” in the setup directory

          Hope that helps, and and any advice as to why this may have occurred would be appreciated.