Quip - Comment Section

Support Extras
1

Can anyone help me with Quip. I have a website that I need users to leave comments to a video. I’m able to download it but want to be able to change the design and text. Is there any documentation on this?

2

The Quip template documentation is all linked at the bottom of this article here: https://docs.modx.com/extras/revo/quip

It’s best to copy them, create your own custom Chunks and then reference your chunks accordingly in your Quip call.

3

Right…do you know how many chunks I have to re-create? Is it the list under files/core/components/quip/elements/chunks? There seems to be 15 there.

Can you tell me also the difference between Non-threaded Comments and Threaded Comments?

4

You’ll have to recreate only as many as you need to customize the design to your taste. Much of what you’ll want to do can be handled by using your own custom CSS and telling Quip not to use it’s (unless you want to override it rather than create your own styles). Basically, if you need to change the code, to get the design the way you want, you’ll want to create a custom Chunk because upgrades will overwrite changes to the Quip templates.

Threaded comments is a setting where you might want to have replies to comments or other replies appear below and in context of the comment replied to, rather than linear comments where each comment is displayed at the same level.

Reddit uses threaded/nested replies, for instance.

I hope this makes sense.

5

This makes perfect sense. I’ve set my threading to ‘1’ as I’d like the idea of it not being linear. Thank you very much. I’m creating new chunks now…will the code inside my html look something like this?

[[!Quip? 
  &thread=`[[*pagetitle]]` 
  &threading=`1`
  &tplComments=`newQuipCommentChunk`
]]
[[!QuipReply? 
  &thread=`[[*pagetitle]]`
]]
6

You might end up with something like this:

[[!Quip?
  &thread=`blog-post-[[*id]]`
  &replyResourceId=`101`
  &closeAfter=`[[*blog.CommentsCloseAfter]]`
  &closed=`[[*blog.CommentsStatus]]`
  &tplComment=`comment`
  &tplComments=`comments_wrapper`
  &gravatarSize=`60`
  &threaded=`1`
  &useCss=`0`
  &limit=`1000`
]]
[[!Quip?
  &thread=`blog-post-[[*id]]`
  &replyResourceId=`101`
  &closeAfter=`[[*blog.CommentsCloseAfter]]`
  &closed=`[[*blog.CommentsStatus]]`
  &tplComment=`comment`
  &tplComments=`comments_wrapper`
  &gravatarSize=`60`
  &threaded=`1`
  &useCss=`0`
  &limit=`1000`
]]

Some of these are optional. I’d avoid using [[*pagetitle]] as your thread reference as it may change and will likely contain spaces. In the examples above, we used blog-post-[[*id]].

In the example above, we also used 2 TVs: blog.CommentsCloseAfter andblog.CommentsStatus`, so we could close comments after a period of time. In our case, we found that 3 weeks was where we stopped getting valuable contributions and spam started rolling in. Closed was boolean and we’d just shut comments on some posts where it wasn’t useful for comment.

7

This is incredibly helpful. Thanks you.

[[!Quip?
&thread=blog-post-[[*id]]
&threaded=1
]]

When I set threaded=1…should I see a reply button beside a comment now?

8

I’ll be honest, I don’t recall, but I think so.