We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Error message after upgrade to 2.7.0

    • 24629
    • 370 Posts
    Ralph Zelf Reply #11, 6 years, 1 month ago
    Hoi
    I also see 
    Support for modAction has been replaced with routing based on a namespace and action name. Please update the extra with the namespace core to the routing based system.

    Namespace core that is MODx itself right?
    RDG
      • 3749
      • 24,544 Posts
      BobRay Reply #12, 6 years, 1 month ago
      Yes, maybe I was wrong, unless some extra is using 'core' as its namespace, which is entirely possible.
        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
        • 17851
        • 213 Posts
        MacLonghorn Reply #13, 6 years, 1 month ago
        So I've got this issue with Batcher and Quip. How do I remove or update these if the Installer doesn't load?
          Mark Macatee
          President
          Power 10 Solutions
          http://www.power10solutions.com
          • 3749
          • 24,544 Posts
          BobRay Reply #14, 6 years, 1 month ago
          First, try turning off the log_deprecated System Settings.

          If that doesn't work, there are some suggestions here if you have the coding skills: https://www.markhamstra.com/modx/2018/deprecated-notices-in-modx-2.7/. Otherwise, you'll have to wait for them 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
            • 18367
            • 834 Posts
            MarkG Reply #15, 6 years ago
            Yeah I'm getting loads of these errors too, seems to be for just about every extra I install.

            To add to the list of known offenders
            RefreshCache
            Gridclasskey

            Those two at least gave a message in the error log that it was them. As for the rest, it looks like this

            [2019-01-08 14:52:26] (ERROR in modProcessor::run @ /home/hotlycom/ampli.buzz/core/model/modx/modprocessor.class.php : 177) Flat file processor support is deprecated since version 2.7.0. 
[2019-01-08 14:52:30] (ERROR in xPDO::getService @ /home/hotlycom/ampli.buzz/core/xpdo/xpdo.class.php : 1234) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2019-01-08 14:52:30] (ERROR in modRestCurlClient::__construct @ /home/hotlycom/ampli.buzz/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.


            Only 10 times longer than that.

            Anyway, turned off the log deprecated function as suggested.

            it's in the System and Server Settings in case anyone's wondering where to find it, about third up from the bottom.


              Content Creator and Copywriter
              • 18373 ☆ A M B ☆
              • 3,141 Posts
              Mark Hamstra Reply #16, 6 years ago
              When you find an extra that needs to be updated, please make sure that there is an issue for it on their respective github issue trackers. In most cases you'll immediately find it just by googling for "modx <extra name> github". Posting a list of offenders in a forum thread will not alert the developers that their extras need an update. If you do list extras here, consider linking to the relevant issue so that people coming along this thread in a year from now will know where to find the current status.

              Some of my extras mentioned here have already been updated, including ClientConfig (as of v2.1) and VersionX (as of v2.2.

              When 2.7.1 comes out, you'll start seeing less errors as a few false positives and core deprecations have been solved. That, in particular, affects the "Flat file processor support is deprecated" warning, which in 2.7.0 is triggered by the config.js.php processor, and the TV getRender one, which was inadvertently being triggered by nearly all TVs instead of only the ones that are actually using old code.
                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.
                • 17851
                • 213 Posts
                MacLonghorn Reply #17, 6 years ago
                Not sure if this is related, but I can't even get a list of Extras. When I view Extras Installer I just get a blank page. The Network log shows a 500 when I request http://<domain>/manager/?a=workspaces. I'm on MODX 2.7.0 and PHP 7.1 (I tried 7.2 as well)
                [ed. note: MacLonghorn last edited this post 6 years ago.]
                  Mark Macatee
                  President
                  Power 10 Solutions
                  http://www.power10solutions.com
                  • 18373 ☆ A M B ☆
                  • 3,141 Posts
                  Mark Hamstra Reply #18, 6 years ago
                  Nope, that does not sound even remotely related to what has been discussed in this thread.

                  For 500 internal server errors, your #1 step is to look at the server error log. In some cases, you can also get to a useful error message by inspecting the request in the browser developer console, network tab.
                    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.
                    • 17851
                    • 213 Posts
                    MacLonghorn Reply #19, 6 years ago
                    Yeah, that's what I was referring to (developer console -> network tab). It only shows 500 but nothing else. I'll open a new thread.
                      Mark Macatee
                      President
                      Power 10 Solutions
                      http://www.power10solutions.com
                      • 53432
                      • 46 Posts
                      zenpixel Reply #20, 6 years ago
                      I get these warnings too since upgrading to 2.7.0.

                      @BobRay, for some time I have used your tutorial on custom DB tables: https://bobsguides.com/custom-db-tables.html

                      Your CreateXpdoClasses snippet is super useful! I’ve used it on many Modx projects over the years. However new that I’m getting these deprecation warnings, I am curious whether the code I generated using CreateXpdoClasses would be causing these warnings? If so, do you have any thoughts on how I would fix that going forward?