We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4749
    • 623 Posts
    I upgraded, well, tried to upgrade and the option wasn’t clickable, but seeing as it was a brand new, tiny site. I decided to backup, install new and just import the .sql. Well, everything was working great until I went to tools > configuration to change site name (oddly it still said MyModx Site or whatever). I hit save and then got all kinds of errors. Now visiting the site there’s a parse error:
    « MODx Parse Error »
    MODx encountered the following error while attempting to parse the requested resource:
    « PHP Parse Error »
     
    PHP error debug
      Error: 	Missing argument 13 for Qm::Qm(), called in /home2/public_html/sitename/manager/includes/document.parser.class.inc.php(746) : eval()'d code on line 2 and defined	 
      Error type/ Nr.: 	Warning - 2	 
      File: 	/home2/public_html/sitename/assets/plugins/qm/qm.inc.php	 
      Line: 	16	 
      Line 16 source: 	function Qm(&$modx, $jqpath, $loadmanagerjq, $loadfrontendjq, $noconflictjq, $loadtb, $tbwidth, $tbheight, $hidefields, $hidetabs, $hidesections, $addbutton, $tpltype, $tplid, $custombutton, $managerbutton, $logout) { 	 
     
    Parser timing
      MySQL: 	0.0006 s	(0 Requests)
      PHP: 	0.0334 s	 
      Total: 	0.0339 s


    Any thoughts
      The MODx has you...
      Utah Web Design
      • 25663 MODX Staff
      • 12,272 Posts
      After importing your 1.0 database, you should run the installer in upgrade mode. If that doesn’t work, you might try re-downloading the files as I suspect one is corrupt and clearing the cache. I can change site names just fine here.
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 4749
        • 623 Posts
        Yeah, that’s what I did and it’s fine now, but hmm... I have no idea why it did that. Weird. Thanks, it’s a great upgrade.
          The MODx has you...
          Utah Web Design
          • 10753
          • 1 Posts
          I ran into this error also, and discovered that by disabling QuickManager (QM) in Home > Elements then select QM+ (my version was 1.1.1 which came which MODx 1.0), then check "Plugin disabled", all the error messages will go away.

          Of course that means you won’t be able to do the quick editing now, so you’ll need to manually upgrade QM+ to version 1.3.3 (http://modxcms.com/extras/package/541). This was actually pretty easy, and the instructions on the package’s download page worked like a charm.

          Kinda surprised that something so fundamental was missed in the 1.0.2 release, but at least this is a workaround.