Support/Comments for Quip-2.0.0-beta1

This is an auto-generated topic for Quip 2.0.0-beta1 by splittingred.

Brief Description:
A simple commenting system for MODx Revolution, complete with a backend management interface, threading support, moderation, notifications, and more.

Note to Those Upgrading:
If you overrode any chunks in QuipReply, you’ll need to update them with the contents in:

&tplAddComment - core/components/quip/elements/chunks/quipaddcomment.chunk.tpl
&tplPreview - core/components/quip/elements/chunks/quippreviewcomment.chunk.tpl

Specifically the extra hidden fields, error message placeholders, and submit button. Also,
notice that preview mode is no longer the default.

New in 2.0.0

• [#3519] Add pre and post Hooks to Quip
• [#3523] Add field-specific error messages, ensure validation of those fields happens on first submit
• [#3518] Enable one-click post options bypassing preview, and added requirePreview property to force preview if wanted
• Fix bug with replyUrl in threaded comments and requireAuth

See official documentation here:
http://rtfm.modx.com/display/ADDON/Quip

Hi,

How can I configure that all new comments are by default ’unapproved’?

Thanks!

[[!QuipReply? &thread=`myThread` &moderate=`1`]]

Quote from: splittingred at Mar 24, 2011, 07:30 AM

[[!QuipReply? &thread=`myThread` &moderate=`1`]]

Thanks. I was already using the parameter &moderate, but the problem was the ’&approved=1’ in my querystring from previous tests Now it works fine!

Hi,

The QuipReply-snippet doesn’t show the form to add new comments. Also no errors are returned.
Am I missing something?

This is what I do:

The Quip-snippet also doesn’t show. When I remove the QuipReply-snippet, the Quip-snippet works fine.

Thanks.

Hello,

I’m relatively new to MODx. I’m still in the process of converting my website to the MODx Templates. So far I’m really enjoying the handiness of the CMS. Thanks to all the developers of the CMS and it’s Packages. So, thats said.

At the moment I’m implementing a blog comment system with Quip to my website. So far everything works really well with all the adjusted templates.
I noticed when I validate the site for example with the W3C Markup Validation Service, I get a few of the following Validation errors:

& did not start a character reference. (& probably should have been escaped as &.)

All the created links (for example the avatar "src"-links or the links for the Post tags) have an "&" character in it. In the HTML5 specification it is recommended to have "&" instead. As described is this article and forum.
I would have created the Ticket myself but I’m not registered and somehow I’m not sure how. :-/

Another suggestion of mine: All links created by a commenter (the "own website" link an all user created links in the comments) should have the attribute rel="nofollow" for search engines in it. So that the SEO of the site can’t be influenced by blog comments. The best would be to have an attribut-variable to additionally insert attributes as "target="_blank".
I would contribute the code but I’m not able enough for it. So I add my suggestions to the community.

I hope I explained everything sufficiently. Thanks for listening.

Greetings

Hi gottkaiser,

Thanks for the input! As for your XHTML &amp issue, you need to set the System Setting ’xhtml_urls’ to Yes. That will fix that.

I’ve also added to the newly-released Quip 2.0.0-pl the rel="nofollow" stuff to Quip, and a new property on QuipReply called &extraAutoLinksAttributes that will take a string of attributes to add to the automatically converted links.

Big thanks for the tip with the "xhtml_urls" option and the fast implementation of the suggested features.

Greetings

I’m loving QUIP, but I "think" I found a bug.

I successfuly set up quip to work on my "web" context, no issues.
My setup uses post moderation.

Unfortunately I cannot get QUIP to work on contexts other than "web" and I receive the following error message:

Fatal error: Call to a member function isMember() on a non-object in /home/sebweb/sebweb-modx-core/components/quip/model/quip/quipthread.class.php on line 41

I tracked this line and it has to do the with the following line of code:

$inModeratorGroup = !empty($moderatorGroups) ? $this->xpdo->user->isMember($moderatorGroups) : false;

If I take that same resource (using my quip template) and move it to the web context, everything work fine. If I move it back to the new context, it stops working.
Also, every page which does not use quip is working perfectly with the new context, so this seems to be specific to QUIP only.


thx for the help

I’m using:
modx revo 2.0.8-pl advanced
CentOS 5.5
MYSQL 5.1.56
PHP 5.3.6
browser: I used FF4, chrome 11+ IE 9

Hi Askarii, can you file that here?

http://bugs.modx.com/projects/quip/