Quip - approved message & notify emails

20 Posts

roadie Reply #1, 15 years, 6 months ago

Hi everyone!
Sorry for posting my topic here. I posted it first on the Quip section, but haven’t got any reply.
So, here is my problem and your help would be greatly appreciated....

I installed latest Quip and I want to have all the comments for my articles moderated. This my Quip call in the template:

[[!Quip? &thread=`[[*pagetitle]]` &threaded=`0` &notifyEmails=`[email protected]` &useGravatar=`0`]]
[[!QuipReply? &thread=`[[*pagetitle]]` &moderate=`1`]]

I receive notifications when new new comments are posted and the the "successMsg" show up when someone is posting a new comment.
All the comments show up when I approve them in the Admin, but:
- the poster doesn’t receive a notification when his comment was approved
- the poster is not notified when new replies are made to that comment even if the "Notify of New Replies" button is checked.

Did I miss anything?
Are there any settings I should change in order to make it work?

Thanks!
Roadie

20 Posts

roadie Reply #2, 15 years, 6 months ago

anyone?

105 Posts

heavensbest Reply #3, 15 years, 6 months ago

I’m having the same issue. But I don’t even get any moderation emails, either.

I had tested the ’Notify me of New Replies’ before and it worked (I think it was in an earlier version), but now it doesn’t.

Here is my snippet calls:

[[!Quip? &thread=`blog-post-[[*id]]` &threading=`1` &idPrefix=`comment-` &useGravatar=`0` &gravatarSize=`45` &tplComments=`OuterComments` &tplComment=`OneComment` &altRowCss=`alt_comment`]]
<br />
[[!QuipReply? &thread=`blog-post-[[*id]]` &recaptcha=`1` &moderatorGroup=`Administrator` &moderators=`[[+my_moderator]]` &recaptchaTheme=`[[++recaptcha.recaptcha_theme]]` &moderate=`1` &idPrefix=`comment-` &closeAfter=`0` &tplAddComment=`LeaveCommentForm` &notifyEmails=`[email protected]`]]

I even tried using the system setting in &notifyEmails and nothing. ie. &notifyEmails=`[[++quip.emailsTo]]`

You may or may not want to use the code I write. It's probably all against the syntax rules of php and MODx.

Carpet Cleaning

105 Posts

heavensbest Reply #4, 15 years, 6 months ago

I think I actually had it working when I didn’t have &moderate=`1` for QuipReply.

You may or may not want to use the code I write. It's probably all against the syntax rules of php and MODx.

Carpet Cleaning

4 Posts

richlocke Reply #5, 15 years, 6 months ago

Hi,
I too am having similar problems. I have Quip and QuipReply all working fine except for &notifyEmails, &moderate and &moderatorGroup. When &moderate=`1` the post appears as if that param doesn’t exist.

I have quickemail installed and that sends emails just fine and debug tells me all the details I expect.

My QuipReply code snippet is:
[[!QuipReply?
&thread=`blog-post-[[*id]]`
&notifyEmails=`[email protected]`
&moderate=`1`
&moderatorGroup=`Moderators`
&closeAfter=`30`
]]

My system details are:
MODx Revo: 2.0.8-pl (traditional - I’m new to MODx, but getting there)
PHP: 5.2.13
Apache: 2.2.3
MySQL: 5.0.77

I followed the "Creating a Blog in MODx Revolutions" tutorial (http://rtfm.modx.com/display/revolution20/Creating+a+Blog+in+MODx+Revolution#CreatingaBloginMODxRevolution-AddingaModeratorGroup) and this is the only bit that is killing me.

Any pointers would be most welcome. I haven’t tried with a previous version of Quip as this is my first adventure into Blogging with MODx.

Thanks

Richard

20 Posts

roadie Reply #6, 15 years, 6 months ago

Now I don’t receive any email at all. This is the error I get:

[2011-04-15 07:48:43] (ERROR @ /index.php) [Quip] Moderator Notifications could not be sent for comment: Array
(
    [id] => 2
    [thread] => Second Page
    [parent] => 0
    [rank] => 0000000002
    [author] => 0
    [body] => Huh?
    [createdon] => 2011-04-15 07:48:43
    [editedon] => 
    [approved] => 
    [approvedon] => 
    [approvedby] => 0
    [name] => Johnny
    [email] => [email protected]
    [website] => 
    [ip] => xx.xx.xx
    [deleted] => 
    [deletedon] => 
    [deletedby] => 0
    [resource] => 2
    [idprefix] => qcom
    [existing_params] => Array
        (
        )

    [nospam] => 
    [auth_nonce] => quip-form-24da84cb79701e
    [preview_mode] => 1
    [notify] => 1
    [comment] => Testing comments
    [quip-post] => 1
)

Formit is sending emails without any problem, I tried even Quickemail and everything works ok.

I’d really appreciate if someone with experience will post an tutorial about Quip. The instructions from http://rtfm.modx.com/display/ADDON/Quip are not very detailed and there are some errors also. eg:

[[!Quip? &thread=`threadNameHere` &threading=`0`]]

instead of [[!Quip? &thread=`threadNameHere` &threaded=`0`]].

Any developer in here? Please help!

4 Posts

richlocke Reply #7, 15 years, 6 months ago

Hi Roadie. Glad it is not just me then. One question, how (and where) did you get the error message? I’ve been looking to track this sort of debug info down for a while. I think I remember coming across some errors/logs somewhere in MODx Revo, but I’ve forgotten where.

Regarding the tutorial, once I’d figured out the typos (such as the &threading vs &threaded you mentioned) and the missing steps (which lead to one of those *oh, that’s where it is* moments), everything went really smoothly. Once I had everything up and running, I was going to contact Bob with my feedback and comments from a ’new to MODx Revo’ user’s perspective. I wouldn’t have had a clue without the tutorial since the documentation seems to be in several places (probably down to migrations from Quip 1.x to 2 and MODx Evo to Revo). It will get there and I will try and be more pro-active in feeding back once I’ve got some success

Richard

105 Posts

heavensbest Reply #8, 15 years, 6 months ago

What versions of Quip are you both using?
I am on 2.0.1. I think it was working in the previous version.

I reported this issue as a bug, not sure if it is a general bug or just specific to us.

@richlocke

For your &moderate, make sure you aren’t logged into the manager (I usually use another browser, then the one I’m logged into the manager with, to test commenting, etc.).

For your &moderateGroup, since you are using a group that isn’t Administrator, did you add the permissions to that group?

When Quip is installed it creates an Access Policy called ’QuipModeratorPolicy’ and assigns that policy to the User Group called ’Administrator’. If you either renamed the User Group that was called ’Administrator’ to something else or want to moderate with a different User Group, you’ll need to see the directions below.
You will need to add this policy to your user group ’Moderators’, if you haven’t.

To do so go to:
- Security -> Access Controls
- User Groups tab -> Right click ’Moderators’ -> Update User Group
- Context Access tab -> Add Context
Context: mgr
Min Role: Member - 9999
Access Policy - QuipModeratorPolicy

That might fix you moderatorGroup issue.

Try to be patient. These guys are writing Modx Evo, Revo, and all these extras. They are especially busy trying to get Revo 2.1 RC3 through it’s testing phase.

You may or may not want to use the code I write. It's probably all against the syntax rules of php and MODx.

Carpet Cleaning

20 Posts

roadie Reply #9, 15 years, 6 months ago

@richlocke
Reports-> Error logs

I also run Modx 2.0.8 with Quip 2.0.1
Please, send updates if you have any success! I was thinking to try it with Quip 1.2.5, the last working version before 2.0.0

@heavensbest
That’s exactly the way I was doing it, with two browsers, but it doesn’t have anything to do with being logged on or not.
Yes, I perfectly understand that the developers are working on 2.1 and I really appreciate their work. If any of you guys is reading this post I want you to know that "You really rock!".

4 Posts

richlocke Reply #10, 15 years, 6 months ago

Quote from: heavensbest at Apr 15, 2011, 09:26 AM

What versions of Quip are you both using?
I am on 2.0.1. I think it was working in the previous version.

I am also on 2.0.1-pl. I know there was some version of something I forgot to include in my original post. Sorry.

I reported this issue as a bug, not sure if it is a general bug or just specific to us.

Great. I wasn’t sure if I should do that just yet since I’m not experienced enough with MODx Revo to provide everything required to make the bug report worthwhile.

@richlocke

For your &moderate, make sure you aren’t logged into the manager (I usually use another browser, then the one I’m logged into the manager with, to test commenting, etc.).

For your &moderateGroup, since you are using a group that isn’t Administrator, did you add the permissions to that group?

When Quip is installed it creates an Access Policy called ’QuipModeratorPolicy’ and assigns that policy to the User Group called ’Administrator’. If you either renamed the User Group that was called ’Administrator’ to something else or want to moderate with a different User Group, you’ll need to see the directions below.
You will need to add this policy to your user group ’Moderators’, if you haven’t.

To do so go to:
- Security -> Access Controls
- User Groups tab -> Right click ’Moderators’ -> Update User Group
- Context Access tab -> Add Context
Context: mgr
Min Role: Member - 9999
Access Policy - QuipModeratorPolicy

That might fix you moderatorGroup issue.

That’s all set up as I have it. I also use two browsers (to check how the CSS is rendering etc) and I also had the DB table open to check what was going in and to get more familiar with how MODx Revo works. Come to think of it, I might have been posting comments using the same browser as I had the manager open in, because I’ve just tried again from a different browser and moderation works (just no mail to either a moderator in the moderatorGroup or to the poster once the post has been approved). But as I said, not a big bug for me, at least it puts my mind at rest that I’m not doing anything stupid.

Try to be patient. These guys are writing Modx Evo, Revo, and all these extras. They are especially busy trying to get Revo 2.1 RC3 through it’s testing phase.

I’ve read that Revo 2.1 RC2 had a nasty bug that caused 2.1 RC3 to come out really shortly thereafter. It isn’t a big bug for me and I know they are doing a sterling job supporting Evo, Revo, Extras and Roadmaps/future releases all at once. One day (I hope) to be able to help out more as I think MODx Revo is going to be a secret gem of a system.

@roadie. Thanks. Found it.