We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22303 MODX Staff
    • 10,725 Posts
    It seems OnHandleRequest was added to the modManagerRequest class early last year, after I originally discussed the context switching plugin. Just add the check as BobRay suggested.
      • 1441
      • 61 Posts
      Sadly, this didn’t work for me. While I DID have a plugin that was switching contexts based on url, I went to the extent of
      - uninstalling all packages
      - re-uploading
      - disabling then *deleting* all my plugins manually (having backups of course)
      - manually emptying the cache
      - restarting the browser and liberally emptying browser caches
      - asking it very, very nicely by means of an uploaded photo of a box of chocolates

      ...yet I still I’m greated with an "Access denied" on the document tree and most other parts of the Manager. I don’t even have permission to logout from the manager.

      Is there anything other than packages, the cache, or plugins that could be causing my woes?

      undecided
      (Thanks!)
        • 3677
        • 130 Posts
        Same symptoms here. I also happen to use a context switching plugin. Disabling it directly in the db did not help.

        I was upgrading from 2.08 to 2.13. I’m trying an interim update now, going from 2.08 to 2.10 first and working my way up.

        -Brian
          • 3677
          • 130 Posts
          Results:

          2.08 - 2.13 - Fail (Access Denied)
          2.08 - 2.10 - OK
          2.10 - 2.13 - Fail (Access Denied)
          2.10 - 2.11 - Fail (Access Denied)

          Now to figure out why.

          -Brian
            • 3677
            • 130 Posts
            Ok, so it appears that I can successfully upgrade to 2.11 or even straight to 2.13 as long as I disable the context switcher plugin BEFORE performing the upgrade.

            I checked it a few times. If I leave it enabled and then upgrade I can’t recover from the "Access Denied" messages even if I disable it via a direct DB edit.

            Maybe this will help someone else who is stuck.

            -Brian