We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28215
    • 4,149 Posts
    splittingred Reply #1, 16 years ago
    This is an auto-generated topic for Quip 1.1.0-pl by splittingred.

    Brief Description:

    A simple commenting system for MODx Revolution, complete with a backend management interface, threading support, moderation, notifications, and more.
    Note: Users who have overridden the default chunks in their installs may need to update those chunks to match the default behavior. The form tag in the &tplComment tpl was removed as of 1.0.1. You will also need to add a call to the QuipReply snippet to show the reply form.
    Note that upgrading to 1.0 changes the markup a bit; comments are now in ol/li tags rather than just divs. If you want to revert back to the old style, set &useMargins=`1` in your Quip call.
    New in 1.1.0

    • Allow QuipCount to take 'user,thread' to simultaneously find all comments by a user in a thread
    • Added "family" option to QuipCount
    • Added theme ability to recaptcha with recaptchaTheme property on QuipReply
    • Added "family" option to QuipLatestComments for finding grouped threads
    • Added QuipResourceCleaner plugin, which removes threads when their Resource has been removed
    • Fixed bug with font-style in web css


    New in 1.0.2

    • Fixed bug with allowRemove parameter
    • Fixed bug with ago filter in QuipLatestComments snippet
    • Fixed bug where pre-existing request parameters werent persisting on links in quip comments
    • Fixed issue where thread was not retrieved before form processing
    • Fixed issue with GET params in approved request
    • Restructured elements in package, cleaned up old files




    Note: After installing, you may need to "Flush All Sessions" (Security - Flush All Sessions) to reload the new Access Policy for the manager interface.
    See official documentation here: http://rtfm.modx.com/display/ADDON/Quip
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
      • 4971
      • 964 Posts
      [[=SOLVED=]]

      In the only post I have so far (in development), I have one comment and
      now it shows the following message:

      This thread has been closed from taking comments.

      How can I open it for comments? I searched in the system settings but there is nothing.
      Can we set the amount of time to leave it open?
      Can it be indefinite on some of them?

      Edit: found the &closeAfter parameter: 0 for indefinite time or a # for the number of days...
        Website: www.mercologia.com
        MODX Revo Tutorials:  www.modxperience.com

        MODX Professional Partner
        • 4971
        • 964 Posts
        Another problem that I am having...

        I use the following code:

        (
        [[!QuipCount? &thread=`blog-post-[[*id]]`]])
        


        in the blog post and it works fine... it shows Comments(1) for the one
        comment I have...

        but when I use the same code in the getResources code in my Blog Post List,
        it shows (0) Comments.

        What am I doing wrong?

        getResources should bring the [[*id ]] of each post right?
          Website: www.mercologia.com
          MODX Revo Tutorials:  www.modxperience.com

          MODX Professional Partner
          • 28215
          • 4,149 Posts
          splittingred Reply #4, 16 years ago
          getResources would use it as [[+id]] in the chunk.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 4971
            • 964 Posts
            Arggghh that’s true, just like in Evo...
            thanks Shaun... sorry.
              Website: www.mercologia.com
              MODX Revo Tutorials:  www.modxperience.com

              MODX Professional Partner