We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34761
    • 11 Posts
    Hi guys,

    I'm hoping someone can help me work this issue out. I upgraded from 2.2.14 to 2.3.3 and have run in to a couple of issues.
    The biggest of which is that I can't save any resources. When trying to save a resource I get the error "Processor not found: update".
    I've attached a screenshot:

    I've started looking through the MODX core but as you can imagine, searching for 'update' and 'processor' gives quite a few results.

    Has anyone else come across this issue either in this scenario or any other?

    Thanks in advance for any help you can give.

    Regards,
    David.

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

    [ed. note: dtgreenwood last edited this post 11 years, 7 months ago.]
      • 10208 ☆ A M B ☆
      • 1,780 Posts
      Try checking compress_css and compress_js in System Settings, set both to off.
      The screenshot isn't working.

      Any chance you used FTP to upload locally unpacked MODX.zip files? If so, reinstall MODX but use your server's file manager and unpack the files on the server, copy/merge to the root and re-run setup.

      http://rtfm.modx.com/revolution/2.x/administering-your-site/upgrading-modx

      EDIT: Make sure to delete your core/cache files, in fact try that first.

        Frogabog- MODX Websites in Portland Oregon
        "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
        Having server issues? These guys have MODX Hosting perfected - SkyToaster
        • 34761
        • 11 Posts
        Thanks Frogabog, I will try your suggestions and I have updated the post to attach the screenshot instead.

        Thanks,
        David.
          • 34761
          • 11 Posts
          An quick update.

          I have check and compression of css and javascript are not enabled.

          Files were uploaded as an archive and extracted on the server directly.

          Cache files were cleared before running the setup which showed no errors.

          I think the way forward may be to try and unpack all the latest files over the top again and re run the setup.
          • discuss.answer
            • 34761
            • 11 Posts
            Hi guys,

            I've solved this issue. I'm assuming something wasn't extracted fully the first time so unzipped the latest version directly on the server and copied the files across using cp on the command line.

            Thanks again Frogbog for your input.

            Regards,
            David.