Quip Issues

Using Quip 2.1.2 on Revo 2.1.3. Everything seems to be working just fine - EXCEPT, whenever a new comment is submitted, no notification email(s) are sent (i.e. to moderators or to users who request to be notified of responses, etc).

When a new comment is submitted, this error is shown in the error log:

[2011-10-21 16:10:32] (ERROR @ /index.php) quipComment: Attempt to set NOT NULL field author to NULL

Other than that, there's no errors and everything is working properly....

Here's my quip calls.

[[!Quip?
&thread=`blog-post-[[*id]]`
&replyResourceId=`123`
&closeAfter=`30`
]]

[[!QuipReply?
&thread=`blog-post-[[*id]]`
&notifyEmails=`emailaddress`
&moderate=`1`
&moderatorGroup=`Moderators`
&closeAfter=`30`
]]

Any thoughts on this?

UPDATE: I've now even allowed the author field to be NULL and adjusted the schema file accordingly (setting null="true") - and still getting the same message. I'm guessing that this is at least contributing to the reason why I can't seem to get a notification email to send, but I could be wrong.... [ed. note: webandflow last edited this post 15 years ago.]

UPDATE: I've now even allowed the author field to be NULL and adjusted the schema file accordingly (setting) - and still getting the same message. I'm guessing that this is at least contributing to the reason why I can't seem to get a notification email to send, but I could be wrong....

It's probably still in the map, which is a file in core/components/quip/model/quip/mysql (-ish).

I suspect that you miscopied it, but your quipReply snippet call looks seriously messed up:



(note what should probably be &notifyEmails)

Have you been able to send emails from your MODX install normally? Think password notifications etc. QuickEmail or SPForm (I think) can help debugging email not being sent if the cause is related to the configuration.

Mark.... Not sure what happened with the copy/paste, but you're right - in the ACTUAL snippet call it's notifyEmails.... it's correct on the site.

Interestingly enough, I JUST upgraded another site from Quip 1.2.x to the current release, adn I'm getting the same error message... I'm going to roll back to the old version and confirm that it's working and see what else I come up with.

I haven't tried sending any other emails from this site, but I'll try a password notification and see what happens.

UPDATE: I AM indeed able to still send activation emails, etc from the site - so that end seems to be working fine.

[ed. note: webandflow last edited this post 15 years ago.]

So....

Turns out, if you don't have a Group called 'Moderators' and you set &moderatorGroup=`Moderators` in your QuipReply call.... no notification emails get sent to the list you provide in notifyEmails.

It seems like these two things SHOULDN'T be connected, right? I'm going to verify in a couple of other installs. Should this be filed as a bug?

If you don't have the group, you wont be able to moderate either.

I haven't checked the actual code but it could be that the code simple stops when it can't find the group, and notifications that are sent later in the process are skipped.

The thing is, though, that I HAVE been able to moderate - my main admin account has been able to see all of the comments in the Quip Manager Page and approve the comments that would come in. Once I approved them, they would show up, as normal on the site. This is part of the reason why it didn't dawn on me to remove the moderatorGroup parameter in the call. Everything worked - except the notifications. It would be nice if Quip threw an error to that effect, or gave some kind of heads up that something was awry other that the cryptic message I was getting.

I think I'll file it and see what @splittingred thinks.....

moderateGroups is for the front-end, there are different permissions for manager users you can set. I can understand the confusion, but just want that clear in case others come across these postings.

I can never hurt to file. If it's not logging into the error log it probably should.

Yeah, I'm going to file it as a "feature request" because I'm not entirely sure it's a BUG per se. But, it would have been helpful to see something like

"No moderator groups 'Moderators' exists.'

Or something to give me a clue....