We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 18367
    • 834 Posts
    Recently I've been getting this error.
    (ERROR @ /home/mysite/core/model/modx/modcontext.class.php : 128) PHP warning: array_merge(): Argument #1 is not an array

    Does anyone know what this means or where I should start looking for debugging?

    I've recently installed some cache management extras to try and improve performance, so maybe that's it.

    Any ideas?

    Thanks
      Content Creator and Copywriter
      • 3749
      • 24,544 Posts
      Any idea what you're doing when that error occurs? That's in the modContext object's getOption() method. It could be called from a lot of different places. It looks like someone is calling it at a time when the context object has not been prepared for use.


      FYI, E_NOTICE errors should be turned off on a production site.


        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
        • 18367
        • 834 Posts
        Quote from: BobRay at Apr 14, 2015, 11:16 PM
        Any idea what you're doing when that error occurs? That's in the modContext object's getOption() method. It could be called from a lot of different places. It looks like someone is calling it at a time when the context object has not been prepared for use.


        FYI, E_NOTICE errors should be turned off on a production site.



        Just accessing a document and saving it.

        In fact just opening any doc will record the error.

        It's exactly the same error all the time.

        It's not affecting the front end in any way that I can see.

        And it's not a production site.

          Content Creator and Copywriter
          • 3749
          • 24,544 Posts
          Sorry, I didn't realize it was a dev. site.

          It's almost certainly a plugin that's causing the problem -- most likely connected to OnDocFormRender or OnDocFormPrerender. If you disable them one by one (starting with the most recently installed), you should be able to figure out which one.
            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