Subscribe: RSS
  • stortzdesignteam Reply #1, 1 year ago
    RSS feed not working and receiving this error in the log.

    Any ideas?

    [2018-01-04 18:11:05] (ERROR @ /var/www/vhosts/ : 453) You should not call uncached elements inside cached!
    Outer tag: [[pdoResources? &parents=`0` &tpl=`ufsRSSItemE` &class=`ufsEvents` &loadModels=`ufsevents` &where=`{"published:=":"1","eenddate:<=":"[[!now]]"}` &fastMode=`0` &showLog=`0` &sortby=`eenddate` &sortdir=`ASC`]]
    Inner tag pdoResources? &parents=`0` &tpl=`ufsRSSItemE` &class=`ufsEvents` &loadModels=`ufsevents` &where=`{"published:=":"1","eenddate:<=":"[[!now]]"}` &fastMode=`0` &showLog=`0` &sortby=`eenddate` &sortdir=`ASC`

    Server and install details:

    OS: CentOS Linux 7.4.1708 (Core)
    Apache web server
    PHP 7.0.24
    Database server:
    Server: Localhost via UNIX socket
    Server version: 5.5.56-MariaDB - MariaDB Server

    Modx 2.6.1-pl
    packages installed:
    • I'm not sure this will help, but here's how I did it:

      The &parents property could be set to any parent.
        Get my Book: MODX:The Official Guide
        MODX info for everyone:
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
      • stortzdesignteam Reply #3, 1 year ago
        This is using a MIGX configuration to pull from, thats why it's using pdoResouces rather than getResources. The feed has been working for over a year until the recent Modx updates. I did try using your method of getResources, which removes the error but the feed still doesn't work.
        • stortzdesignteam Reply #4, 1 year ago
          Got the error to go away by placing a bang! in front of pdoResources. Unfortunately, the feed still doesn't want to pull data from the Migx configuration.
          • W. Shawn Wilkerson Reply #5, 8 months, 2 weeks ago
            You could try spiefeed in the repository. It always worked for me.

              Get your copy of MODX Revolution Building the Web Your Way

              Check out my MODX || xPDO resources here:
            • For web searchers researching this error:

              I found a more trivial cause for this error, we had a chunk that an updater person had copied in wrong: [[$chunkname?value=`something`]

              They'd left off the closing ]. That then tripped a huge modx error log, with all the rest of the page template html logged, and of course, nothing after that error printed in the html of the page.

              Finding this is very difficult, I was very lucky because the rest of the template html contained a pointer in the html to which page it was, otherwise I would never have been able to find it. [ed. note: lizardx last edited this post 7 months ago.]
              • I wonder if this would cause the same problem:

                 [[$chunkname?value=`something`] ]

                I just mentally wrote a check that would test the page and chunk content for these:

                if (substr_count($content, '[[') !== substr_count($content, ']]') {
                   /* Error */

                If I find time, maybe I'll build it into SiteCheck.
                  Get my Book: MODX:The Official Guide
                  MODX info for everyone:
                  My MODX Extras
                  Bob's Guides is now hosted at A2 MODX Hosting