We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36575
    • 104 Posts
    The comment thread is not displaying on the front end. They appear in the back end as approved.

    Nothing is rendered in the HTML (it's like the snippet call is being ignored)

    there is nothing in the error log

    I have Quip 2.3.1
    modx revolution 2.2.2
    not sure of php version (will check with host)MySQL server version 5.0.51a
    My snippet call is

    [[!Quip?
    &thread=`comments-[[*id]]` &threading=`0`
    ]]

    [[!QuipReply? &thread=`comments-[[*id]]`]]

    my test page is
    http://www.podgarden.co.nz/testing-comments.html

    I have:
    Uninstalled Quip and re-installed 4 times
    Deleted the following tables from the database manually:
    modx_quip_comments
    modx_quip_comments_closure
    modx_quip_comment_notify
    modx_quip_threads
    flushed permissions
    deleted cache
    cleared browser cache

    when i install quip i get the attached errors, but it tells me it installed ok
    • MySQL 5.0.51 could be an issue: http://rtfm.modx.com/display/revolution20/MySQL+5.0.51+Issues

      Also, please put code snippets in code tags, as there might be some tags getting eaten there.
        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.
        • 36575
        • 104 Posts
        Thanks Mark. I do have Quip running on another site with the same host and same setup, but I suspect the issue must be to do with the update. I initially had quip from the blogging essentials package, and had to force remove it.
        I'm about to do some tests locally and see if I still have the same problem, or if it's the mySQL that's causing it not to work.
          • 36575
          • 104 Posts
          Hi,

          Wondering if anyone is able to help me with this one.

          I have moved this site to a new server, and I'm still having similar issues. If anything, the issues are worse! I now get a memory allocation timeout error so I can't even see the page.

          -upgraded to quip 2.3.2

          new server specs
          Apache/2.2.16 (Debian)
          MySQL client version: 5.1.63
          PHP Version 5.3.3-7+squeeze13

          modx revolution 2.2.2

          My snippet call is

          [[!Quip? &thread=`pod[[*id]]` &threaded=`0`]]
          <br>
          [[!QuipReply? &thread=`pod[[*id]]`]]


          If I just include the QuipReply call, I get the form, and no issues. If I include the Quip call, and then submit a comment, I get the form displayed twice, eg
          http://www.podgardening.co.nz/asparagus.html?quip_approved=1#qcom2

          If I try and load a page that has the quip call aboe for the first time, I get a fatal memory error like this one: http://www.podgardening.co.nz/beetroot.html

          Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 261900 bytes) in /var/virtual/podgarden/www.podgardening.co.nz/html/core/xpdo/om/xpdoobject.class.php on line 116

          This one is on a page where quip is the ONLY thing apart from the logo.
          http://www.podgardening.co.nz/testing-comments.html

          Attached is the text I got when upgrading quip. It had loads of errors, but said it installed fine.



            • 36575
            • 104 Posts
            I've removed the quip call from all pages except this one for now, as the client is in the process of adding content and testing....

            http://www.podgardening.co.nz/testing-comments.html

            Any help or suggestions on how to get this to work would be gratefully received.
              • 36575
              • 104 Posts
              I have upgraded to Revolution 2.2.4, and reinstalled quip (manually deleting database tables again) and I still have the same issue. Any suggestions?