We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
  • Hi all,
    after updating from 2.3.2 to 2.5.7, everything seemed fine until trying to open a ressource in manager. Ressources tree is there, search does show titles, but clicking on the ressource will throw a php error:
    Fatal error: Uncaught Error: Call to a member function get() 
    on array in [...]/manager/controllers/default/resource/resource.class.php:152 Stack trace: 
    #0 [...]/core/model/modx/modmanagercontroller.class.php(158): ResourceManagerController->firePreRenderEvents() 
    #1 [...]/core/model/modx/modmanagerresponse.class.php(74): modManagerController->render() 
    #2 [...]/core/model/modx/modmanagerrequest.class.php(180): modManagerResponse->outputContent(Array) 
    #3 [...]/core/model/modx/modmanagerrequest.class.php(128): modManagerRequest->prepareResponse() 
    #4 [...]/manager/index.php(58): modManagerRequest->handleRequest() 
    #5 {main} thrown in [...]/manager/controllers/default/resource/resource.class.php on line 152


    Can anybody give a hint what to do?

    Best,
    Brigitte

    This question has been answered by markh. See the first response.

    [ed. note: BrigitteB last edited this post 6 years, 9 months ago.]
      Brigitte Bornemann - Accessibility Consultant, Web Designer - Hamburg / Munich, Germany.
      http://www.bit-informationsdesign.de
      • 3749
      • 24,544 Posts
      Did you skip the versions in between? It's important to upgrade to the .0 versions when making a jump (in this case 2.4.0 and 2.5.0).

      Also, it's common to see weirdness in the Manager after an upgrade caused by old MODX cache files and/or left-over browser cache files and cookies. Manually deleting all files in the core/cache directory may help (if you used UpgradeMODX, it did that for you). You can visit with your browser in incognito or private mode to take the browser cache and cookies out of the equation. If that fixes things, you need to clear the browser cache and cookies for the site.

      If none of that helps, it could be a plugin that's not compatible with the new version of MODX, or one that needs to be upgraded.



        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
      • discuss.answer
        Update TinyMCE. That has a conflict that causes the error you're seeing.
          Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

          Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • It was TinyMCE, thanks, Mark.

          I'm happy that it is not the big version jump, as Bob indicated, what would mean a lot of work. But I will take this tip to my procedures: never skip the 0 of a new main version.

          Thanks a lot
          Brigitte
            Brigitte Bornemann - Accessibility Consultant, Web Designer - Hamburg / Munich, Germany.
            http://www.bit-informationsdesign.de
            • 3749
            • 24,544 Posts
            I don't use TinyMCE myself so I always forget about that issue. I'm glad Mark chimed in.

            Since you did skip versions, keep an eye out for error messages in the log referring to an "unknown field" in a database query.

            If one turns up, see this article: https://bobsguides.com/blog.html/2016/06/27/missing-db-fields-(unknown-column)/.
              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