We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28104
    • 8 Posts
    Hi,
    I upgrade my website (which was running 2.2.11pl - yeah I know, I should have upgraded before).
    It is not the first time I do so, and usually it goes without (too much) problems.

    This time, the upgrade script went fine, I was able to log back into the manager (which looks good btw) and updated my packages.
    Then I decided to put my website out of the «Maintenance mode»
    I clicked on the cog icon in the top right and selected System Settings...

    I get the top page, with the header of the "standard" display of the settings, but nothing get listed, instead I get an error: «Processor not found: getlist»
    When trying to «Filter by area...», I get the following:
    Code: 404 Not Found
    {"success":false,"message":"Processor not found: getareas","total":0,"data":[],"object":[]}


    Help? Anyone?
    I would like to put my website out of maintenance mode asap...

    I tried to empty the cache both on the site end and browser end; I tried a different browser; I re-run the upgrade process (I do it through SSH, not FTP); but no luck so far

    Thanks
      • 28104
      • 8 Posts
      I was able to get my site back up by going in the db and changing back the value in modx_system_settings for site status from 0 to 1.

      The website itself seems to be OK (I haven't tested everything but I will)

      However I still have the issue with System Settings
      I'm still getting the same errors message:
      Processor not found: getlist
      instead of the list of my settings and:
      Code: 404 Not Found
      {"success":false,"message":"Processor not found: getareas","total":0,"data":[],"object":[]}

      when trying to «Filter by area...»

      I must add that I do get the same Code: 404 Not Found... when looking at other settings than core (eg. codemirror, formit, etc...)

      Nobody with this issue?
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        How did you update the files? This sounds like missing or corrupted files. Try uploading the entire .zip archive and unzipping it on the server, moving the files into place, and run setup again. Or you could try this script and let it handle the upload and extracting of the files.

        https://github.com/sottwell/installer
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 28104
          • 8 Posts
          Quote from: sottwell at Aug 15, 2014, 02:24 AM
          How did you update the files? This sounds like missing or corrupted files. Try uploading the entire .zip archive and unzipping it on the server, moving the files into place, and run setup again. Or you could try this script and let it handle the upload and extracting of the files.

          https://github.com/sottwell/installer

          I did my upgrade the way I usually do it:
          SSH login on the webserver and then command line for the following:
          - download package using wget
          - unzip package into a temp folder
          - copy the content of the unzipped folder to my modx install
          and then run the setup from my Internet browser


          Now, as I mentioned, I ended up with errors.
          I tried the re-install -> no luck
          I downloaded the package locally and uploaded via SCP -> still no luck
          I then went to every single cache or temp files/folders I could find (on the webserver, in db, in Internet browser...) and clear them all,
          then didn't get a chance to go back to it for a day or two (blessed are the week-ends!)

          and yesterday... it worked (?!?!)

          So not sure what made it worked... but it is OK now...
          Seems like a cache or temp file somewhere but obviously not my browser's cache or /core/cache as I had clean them before without fixing my issue.

          I'm a bit puzzled, happy but puzzled...

          Thanks for your help anyway!

            • 33238
            • 388 Posts
            Hello...

            I had the same problem, the warning message when I try open a chunk or the system Settings.

            Code: 404 Not Found
            {"success":false,"message":"Processor not found: getareas","total":0,"data":[],"object":[]}


            After read this I:

            - Logout from ModX
            - Delete the core/cache files manually (by FTP).
            - Delete the browser cache (Chrome) Shift+Alt+Del.
            - Login

            And that was all SOLVED!!!

            Hope that helps! smiley
              --
              ysanmiguel.com