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

Support/Comments for Quip 1.0.1-pl

    • 28215
    • 4,149 Posts
    splittingred Reply #1, 16 years, 1 month ago
    This is an auto-generated topic for Quip 1.0.1-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.0.1:

    • Properly redid ol/li support to properly nest tags
    • Removed form tag in comment tpl

    New in 1.0.0:

    • Added pagination support for threads via the &limit property and other templating options
    • Now no longer any need to mirror calls in QuipReply in threaded comments; pulls from original QuipReply call on source page
    • Emails for moderators now have direct moderation links within them to approve/reject a comment
    • Comments are now threaded properly with ol/li tags
    • Added disableRecaptchaWhenLoggedIn property to QuipReply that defaults to true which skips recaptcha for logged in users
    • Added dontModerateManagerUsers property to QuipReply that defaults to true which skips moderation for users logged into mgr
    • Snippet properties are now i18n compat


    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://svn.modxcms.com/docs/display/ADDON/Quip
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
      • 1434
      • 23 Posts
      An-tonio Reply #2, 16 years, 1 month ago
      I have update to this version and find the next problem:

      PHP Fatal error: Call to a member function checkPolicy() on a non-object in /.../core/cache/elements/modsnippet/42.include.cache.php on line 111

      it seem that when its the firs time a thread is created it tried so use $thread object before it’s created. If the treath already exits, it’s not a problem.

      I have solve it changing the next line from:

      $isModerator = $thread->checkPolicy(’moderate’);

      to:

      if (is_object($thread)) $isModerator = $thread->checkPolicy(’moderate’);
        • 17499 ☆ A M B ☆
        • 872 Posts
        lossendae Reply #3, 16 years, 1 month ago
        Thanks for the fix.

        Did you post it on the github page?
          • 1434
          • 23 Posts
          An-tonio Reply #4, 16 years, 1 month ago
          Done...

          And may be another issue, before open an issue in github I prefer to discuss it here to see if it’s an issue or my fault using quip.

          I’m using custom friendly urls to access multiple database entries and using an unique modx resource, I set a different thread for each entry using an snippet call. So when I access:

          /friendly/url/to/entry/entryid

          in a plugin attached to OnPageNotFound I sendForward to /modxresource.html?id=entryid

          until this ok, in the template for this resource I have quip as show:

          [[!Quip? &thread=`Entry [[getReqParam? name=`id`]]` &threading=`0`]]


          [[!QuipReply? &thread=`Entry [[getReqParam? name=`id`]]`]]

          when I click in "Preview" a post it send to /modxresource.html?id=entryid#quip-comment-preview-box-qcom correctly but when I click in "Post" it send me to /modxresource.html?quip_approved=1#qcom7 and list de id=entryid query url and lost de entry.

          Any suggestion or an issue ?

          "Close" button work ok and send back to /modxresource.html?id=entryid
            • 1434
            • 23 Posts
            An-tonio Reply #5, 16 years, 1 month ago
            Well, I think it’s an issue too, I change:

            $url = $comment->makeUrl('',array(
    'quip_approved' => $comment->get('approved') ? 1 : 0,
));


            by

            $params = $modx->request->getParameters();
$params['quip_approved'] = $comment->get('approved') ? 1 : 0;
$url = $comment->makeUrl('',$params);


            on line 86 in QuipReply snippet.

            Github issue opened...
              • 3688
              • 43 Posts
              bnetz Reply #6, 16 years, 1 month ago
              Hi,

              I have installed Quip and want to use reCaptcha, but when I activate it it tells me in the frontend
              To use reCAPTCHA you must get an API key from http://recaptcha.net/api/getkey

              It does not work to enter my key in the MODx-Manager under System -> Settings -> recaptcha.public_key . I doubleclick on the "recaptcha.public_key", enter my valid key (see screenshot attached), but afterwards nothing has changed. Other settings I can change in the System -> Settings-Area.

              Is there some hint for me?

              Thanks in advance!

              (Revo 2.0.0-pl trad.).

              Possibly I have to install another component which is not mentioned in the (very good!) tutorial to set up a blog with modx?
                • 20308
                • 31 Posts
                wildcat Reply #7, 16 years, 1 month ago
                Hi,
                The key needs to be entered in the value field (wert)
                  • 3688
                  • 43 Posts
                  bnetz Reply #8, 16 years, 1 month ago
                  Uah! Just didn’t see the field and doubleclicked on the "name"-field shocked

                  Thank you very much for your hint!

                  (my case closed)