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

    I've updated the MODX install of the German MODX Community at http://de.modx.com

    After the update discuss fails to load with eigher max_execution_time or memory_size php errors:
    [22-Jan-2014 11:59:56 Europe/Berlin] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /core/xpdo/om/xpdoobject.class.php on line 1849
    [22-Jan-2014 12:00:15 Europe/Berlin] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /core/model/modx/modelement.class.php on line 197
    [22-Jan-2014 12:03:15 Europe/Berlin] PHP Fatal error:  Maximum execution time of 100 seconds exceeded in /core/model/modx/modparser.class.php on line 232
    [22-Jan-2014 12:08:08 Europe/Berlin] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /core/model/modx/modelement.class.php on line 315
    [22-Jan-2014 12:17:50 Europe/Berlin] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 130968 bytes) in /core/model/modx/filters/modoutputfilter.class.php on line 349
    [22-Jan-2014 12:30:32 Europe/Berlin] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /core/xpdo/om/xpdoobject.class.php on line 0
    [22-Jan-2014 12:37:39 Europe/Berlin] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 110 bytes) in /core/model/modx/modlexicon.class.php on line 179
    


    Any ideas how to bring discuss back to life?


    Environment Info
    MODX 2.2.11 (2.2.8 before update)
    Discuss 1.2.2
    PHP 5.4.21
    MySQL 5.5.32
    Apache Server

    This question has been answered by multiple community members. See the first response.

    [ed. note: christianseel last edited this post 10 years, 3 months ago.]
      chsmedien - Digital Marketing Agency
      MODX Professional & Ambassador

      http://chsmedien.com | http://twitter.com/christianseel
    • Problem identified. Seems do be related to the custom theme. With the default theme the forum loads without issues.
        chsmedien - Digital Marketing Agency
        MODX Professional & Ambassador

        http://chsmedien.com | http://twitter.com/christianseel
      • discuss.answer
        Sounds like something is going into a recursive loop.
          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
        • discuss.answer
          Susan you're correct! Thats the line that causes the problems:
          <meta name="description" content="[[*description:default=`[[*content:striptags:ellipsis=`200`:escape]]`]]" />


          [[*content]] in the content of the ressource - that sounds like an recursive loop...
          I'm curious why this happened not before in MODX 2.2.8?

          Anyway after the update and without this "content in content" discuss feels a little bit faster smiley
            chsmedien - Digital Marketing Agency
            MODX Professional & Ambassador

            http://chsmedien.com | http://twitter.com/christianseel
          • A meta tag is in the template head, not the content, so using the [[*content]] tag there shouldn't be a problem. In fact, testing your exact meta tag in one of my new 2.2.11 installations works fine. Something else is in play here, but if removing that line fixes the problem I suppose all's well that ends well.
              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
            • In this case the meta tag was in the wrapper template of discuss. Discuss in this case is a snippet that is called in the content field of a resource...
                chsmedien - Digital Marketing Agency
                MODX Professional & Ambassador

                http://chsmedien.com | http://twitter.com/christianseel
              • Ah, that does complicate matters. Indeed, it does seem a puzzle that it ever worked at all. Perhaps something stopped the looping at some point before; that would account for the apparent speed improvement.
                  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