Not sending e-mails
dani matielo - July 28, 2009 - 22:41
| Project: | Comment Notify |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Hello, I have installed the last stable version of this module in both a 6.x and 5.x websites and none of them seem to work. I have checked the logs and there is not trace of Comment Notify there. I had comment mail and akismet comment e-mail activated. Disabled both and still nothing happens when I sign up to receive updates: not when I am logged and not when I am not logged. I have checked the permissions and configurations of the module and everything seems to be working correctly - except that it doesn't send any notification. Any help is greatly appreciated.
#1
That's...quite odd. I'm not sure what to say. The module works for thousands of people :/
Maybe try again on a new installation?
#2
Is there any other know incompatibility between this and other Drupal modules that maybe could solve the problem? Are the e-mails expected to be sent right away or on cron run?
Thank you for your help,
Dani
#3
They should be sent right away. It also performs a "watchdog" for each mail that is sent (which is a bit much, but useful in situations like this).
Can you look in the comment_notify database table and see if there are any records where the notify column is not zero?
Also, it doesn't send notifications for your own comments. Maybe that's what is causing the confusion?
#4
#5
Same problem here with D6.
I have 5101 rows in the comment_notify table and all with the notify column at 0.
Any idea? Thanks in advance.
#6
If they are all at 0 then either nobody is subscribing to notifications or there is a problem with the way that they are being saved.
I don't use 5.x any more so I would have a hard time to debug where the problem is. I suggest trying this a bit more and looking in that database table to see what is or isn't being stored.
#7
So, for your words, it must be a problem with the way comment notify on my D6 site saves the "subscription" status on comment submission.
I will take a look tomorrow. Any special thing to look at?
Thanks in advance, Simon.
#8
As noted,
comment notify is not saving in the database the "notify" status, so no one in never notified.
This is the form source code:
<form action="/comment/reply/1276" accept-charset="UTF-8" method="post" id="comment-form">
<div><div class="form-item">
<label>Su nombre: </label>
<a href="/usuarios/testsite" title="Ver perfil de usuario.">testsite</a>
</div>
<div class="form-item" id="edit-comment-wrapper">
<label for="edit-comment">Comentario: <span class="form-required" title="Este campo es obligatorio.">*</span></label>
<textarea cols="60" rows="30" name="comment" id="edit-comment" class="form-textarea required"></textarea>
</div>
<fieldset class=" collapsible collapsed"><legend>Formato de entrada</legend><div class="form-item" id="edit-format-1-1-wrapper">
<label class="option" for="edit-format-1-1"><input type="radio" id="edit-format-1-1" name="format" value="1" checked="checked" class="form-radio wysiwyg wysiwyg-format-1 wysiwyg-editor-fckeditor wysiwyg-field-edit-comment wysiwyg-status-1 wysiwyg-toggle-0 wysiwyg-resizable-1" /> Filtered HTML</label>
<div class="description"><ul class="tips"><li>You can use <a href="/filter/tips/1#filter-bbcode-0">BBCode</a> tags in the text.</li><li>HTML tags will be transformed to conform to HTML standards.</li><li>You may quote other posts using [quote] tags.</li><li>Glossary terms will be automatically marked with links to their descriptions. If there are certain phrases or sections of text that should be excluded from glossary marking and linking, use the special markup, [no-glossary] ... [/no-glossary]. Additionally, these HTML elements will not be scanned: <em>a, abbr, acronym, code, h1, h2, h3, pre</em>.</li></ul></div>
</div>
<div class="form-item" id="edit-format-2-1-wrapper">
<label class="option" for="edit-format-2-1"><input type="radio" id="edit-format-2-1" name="format" value="2" class="form-radio wysiwyg wysiwyg-format-2 wysiwyg-editor-none wysiwyg-field-edit-comment wysiwyg-status-1 wysiwyg-toggle-1 wysiwyg-resizable-1" /> Full HTML</label>
<div class="description"><ul class="tips"><li>Las direcciones de las páginas web y las de correo se convierten en enlaces automáticamente.</li></ul></div>
</div>
<div class="form-item" id="edit-format-3-1-wrapper">
<label class="option" for="edit-format-3-1"><input type="radio" id="edit-format-3-1" name="format" value="3" class="form-radio wysiwyg wysiwyg-format-3 wysiwyg-editor-none wysiwyg-field-edit-comment wysiwyg-status-1 wysiwyg-toggle-1 wysiwyg-resizable-1" /> Texto enriquecido</label>
<div class="description"><ul class="tips"><li>Las direcciones de las páginas web y las de correo se convierten en enlaces automáticamente.</li><li>Etiquetas HTML permitidas: <a> <p> <span> <div> <h2> <h3> <strike> <img> <hr> <br> <br /> <ul> <ol> <li> <table> <tr> <td> <em> <u> <em> <strong> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <code> <cite> <embed> <object> <strike> <caption> <thead> <th> <param> <center></li><li>Saltos automáticos de líneas y de párrafos.</li><li>Glossary terms will be automatically marked with links to their descriptions. If there are certain phrases or sections of text that should be excluded from glossary marking and linking, use the special markup, [no-glossary] ... [/no-glossary]. Additionally, these HTML elements will not be scanned: <em>a, abbr, acronym, code, h1, h2, h3, pre</em>.</li></ul></div>
</div>
<div class="form-item" id="edit-format-4-1-wrapper">
<label class="option" for="edit-format-4-1"><input type="radio" id="edit-format-4-1" name="format" value="4" class="form-radio wysiwyg wysiwyg-format-4 wysiwyg-editor-none wysiwyg-field-edit-comment wysiwyg-status-1 wysiwyg-toggle-1 wysiwyg-resizable-1" /> PHP code</label>
<div class="description"><ul class="tips"><li>You may post PHP code. You should include <?php ?> tags.</li><li>Saltos automáticos de líneas y de párrafos.</li><li>Las direcciones de las páginas web y las de correo se convierten en enlaces automáticamente.</li><li>Glossary terms will be automatically marked with links to their descriptions. If there are certain phrases or sections of text that should be excluded from glossary marking and linking, use the special markup, [no-glossary] ... [/no-glossary]. Additionally, these HTML elements will not be scanned: <em>a, abbr, acronym, code, h1, h2, h3, pre</em>.</li></ul></div>
</div>
<div class="form-item" id="edit-format-5-1-wrapper">
<label class="option" for="edit-format-5-1"><input type="radio" id="edit-format-5-1" name="format" value="5" class="form-radio wysiwyg wysiwyg-format-5 wysiwyg-editor-none wysiwyg-field-edit-comment wysiwyg-status-1 wysiwyg-toggle-1 wysiwyg-resizable-1" /> Texto plano</label>
<div class="description"><ul class="tips"><li>Etiquetas HTML permitidas: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd></li><li>Saltos automáticos de líneas y de párrafos.</li></ul></div>
</div>
<p><a href="/filter/tips">Más información sobre opciones de formato</a></p></fieldset>
<input type="hidden" name="form_build_id" id="form-eff3f1af6e8cae5fe2524a4a4d4018a8" value="form-eff3f1af6e8cae5fe2524a4a4d4018a8" />
<input type="hidden" name="form_token" id="edit-form-token" value="c7795b31cff03cc551d7f486e7a2c97d" />
<input type="hidden" name="form_id" id="edit-comment-form" value="comment_form" />
<div class="clear-block">
<div class="form-item" id="edit-notify-wrapper">
<label class="option" for="edit-notify"><input type="checkbox" name="notify" id="edit-notify" value="1" class="form-checkbox" /> Suscríbeme por correo a los comentarios en este hilo</label>
</div>
<input type="hidden" name="notify_type" id="edit-notify-type" value="0" />
</div>
<input type="submit" name="op" id="edit-preview" value="Previsualizar" class="form-submit enviarcomentario comm-previa" />
<input type="submit" name="op" id="edit-submit" value="Guardar" class="form-submit enviarcomentario comm-enviar" />
</div></form>
Any idea of what can be the problem? Thanks in advance!
#9
+1
No mail being sent to node author.
comment_notify_user_settings has a 1 in node_notify & comment_notify.
Of my two test comments, one has a 1 in notify and notified, the other has a 0.
I have my configuration set to moderation. One of them I approved.
Watchdog has no entries for this module.
Cron has run since approving the comment.
I did check my bulk mail folder.
Using 6.x-1.2.
#10
same thing happens here as #9. I thought there is something wrong on my side after searching the issue queue i came to know that it happens to many of us. I am tempted to mark this as bug. You have set the status to "postponed (maintainer needs more info)" . Please let us know what information you need.
#11
The module works fine for me...so, I can't debug this :/
Someone who suffers from it will have to debug themself.
#12
My emails are also not going out, and I have nothing showing up in my drupal logs.
#13
I've actually experienced the same issue.
Ultimately I found another module has implementing hook_comment and running before comment_notify.
Updating the weight in the system table so our custom module would run after seemed to solve this issue.
#14
Very interesting.
It's always a good debugging step to start disabling all the modules on your site one by one to see if that fixes it.
#15
Note that #617070: Doesn't record subscription when only one subscription type is enabled (and lots more tests) is a potential cause of the problem - can folks confirm that issue/solution?
#16
I am also having this problem. I'm running Acquia Drupal (6.14) on BlueHost... it uses comment_notify v. 6.x-1.2. Only the Admin is set to receive comments, and the values in comment_notify_user_settings are all 1 for uid 1. I logged out and added comments anonymously. In comment_notify table, notify = 0 and notified = 0 . No log entries appear about sending notification.
Per #13, I tried changing the weight of comment_notify to -5 in the system table. It didn't help. Tried to uninstall and reinstall the module, it didn't help. Tried adding a new user (not admin user) to receive comment notifications, same results.
The only non-Acquia modules I'm using are:
AddtoAny
Ctools
FLVmediaPlayer
Panels
PorterStemmer
SpamSpan
SWFObject_API
WYSIWIG
#17
It's interesting that "notified = 0" for your records. Can other people confirm this?
Do you allow comments to be published directly or do they go into the moderation queue?
@barckhoff - it would also be helpful if you upgraded to the latest 6.x-1.x-dev to see if that fixes the problem for you. Thanks for your help debugging.
#18
OK, so I just installed the SMTP Authentication module for sending mail and now it sends the emails. Is SMTP (or similar) required for this module? If so, it would be good to add this to the INSTALL.txt file. Or is that some server configuration issue because I'm on a hosted site?? (sorry if I'm a bit clueless, but I'm sure others are too).
However, as it turns out, I had set Authenticated users to be published directly and Anonymous to be sent to the queue. As it turns out, the Authenticated user comment notifications were being sent, but the Anonymous comment notifications were not. When I ticked the "post comments without approval" for Anonymous user Permissions, the email was sent.
So, it seems there's an issue with the queue function.
Will try the dev version & let you know...
#19
barkchoff - there is no dependency on smtp but if your site has trouble sending mails then this module will too.
The queueing system should work whenever the queued comments are published, but that capability is relatively new and may not be in 6.x-1.2 version. That's why I suggested trying the 6.x-1.x-dev. I will be making a new official release soon - having more testers report problems is helpful to making sure that it's the right time, so thank you for your help!