Closed (fixed)
Project:
Project issue tracking
Version:
5.x-2.x-dev
Component:
Mail
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
13 Jan 2008 at 15:15 UTC
Updated:
3 Jun 2008 at 19:32 UTC
Jump to comment: Most recent file
Comments
Comment #1
aclight commentedDid you change your subscription settings before the Role contact project was created? If so, that's the problem. The code that handles subscriptions actually subscribes you to each project that you select at the time you edit the settings. If a project doesn't exist at the time you edit your settings, you won't be subscribed to it later when it is created. You need to periodically go back and edit your settings and click the own issues button for all projects and save.
So, to check this, just view your subscription settings right now. I'm guessing that for the role contact module, it will show you as having no subscriptions. If that's the case, then this is a duplicate of http://drupal.org/node/177318 and if would be great if you could set the status to show that. If that's not the case this might be a separate issue, but someone with drupal db access would probably need to check this out to see if the db shows you as being subscribed or not.
Comment #2
GoofyX commentedI just checked the subscription settings. The Role contact module is set to 'Own issues'. There are of course other modules that are set to 'None'. So, I guess this is a bug of some kind.
And no, I had not changed the subscriptions before filing the issues. The reason I checked the subscription settings is the e-mail problem I'm describing here, just to confirm that the correct settings are set.
Update: I just got an e-mail for this specific comment...
Comment #3
GoofyX commentedPlease, any idea about this? Am I the only one experiencing this behaviour?
Comment #4
GoofyX commentedRight. Now I get e-mail notifications.
I will mark this closed...
Comment #5
GoofyX commentedHm... Same behaviour again. This time for the Event module (issue is here).
Comment #6
hunmonk commentednobody else is reporting this, and we can't replicate it.
Comment #7
GoofyX commentedIt seems to be ok now. I will reopen the issue if this happens again.
Comment #8
GoofyX commentedForgot to change status.
Comment #9
GoofyX commentedI'm reopening this issue, because it happened again. This time, I think I have found a pattern this occurs.
It seems that when I create an issue, I always do not get the first message for it (the node without the comments) and maybe a couple of the first two or three comments. This happened again when I opened an issue for Drupal. I did not get the first message for the issue, plus with the messages up to (including) #3. I got two messages for #4 and #5. For the current issue, I checked my mails and saw that I did not get the first message and the message for comment #1.
Could this help?
Comment #10
aclight commentedMy gut feeling is that this is not a problem with the project issues module itself.
The only time I have seen this kind of behavior is when I thought I was subscribed to get issues (all or my own) from a project but wasn't actually subscribed to that project.
It could also be that the mail is getting lost/discarded/removed from plain sight somewhere along the way due to a spam filter or some other kind of filter. I have email from my d.o account go to gmail, and I haven't had any problems with them putting issue emails in my spam folder.
As hunmonk said above, you seem to be the only one reporting this problem.
Please check your mail applications settings as well as those of your ISP or upstream provider to see if somehow things are getting lost along the way. If as far as you can tell things there are good then please move this issue into the D.o infrastructure queue, as this will need to be investigated by someone with admin access to the d.o servers.
Comment #11
GoofyX commentedaclight, thanks for the answer.
I am using the same e-mail account to get the messages as the one I use with the Drupal mailing lists (development, translations, document, support, themes), where I seem not to have missed a single message. Of course, I was subscribed to the Drupal project (own issues) for a long time now.
Thanks, anyway.
Comment #12
aclight commentedComment #13
aclight commentedOk, I can confirm that this is indeed happening.
For some time now, I have been subscribed to "own issues" for the Views issue queue.
A week ago, I created 4 new issues in that queue.
Of those 4 issues, I have not received *any* of the follow up email notifications for 3 of the issues:
#254325: Include a null argument
#254347: WSOD when viewing a page (or views preview of a page) with an attachment attached
#254340: Add and rearrange buttons are not properly aligned in Safari
For the 4th issue, I *did* receive all follow up email notifications:
#254350: Validator select box and options sometimes cannot be selected in FF
I have searched through gmail (including my spam and trash folders) for signs of these first three issues and I got neither the original issue nor any followups sent to me.
That being said, I can't think of why this would be happening.
As a point of information, all 4 of these issues are correctly listed on my "My issues" page at http://drupal.org/project/issues/user
Comment #14
aclight commentedI believe I've uncovered the problem here (or at least part of the problem).
Take a look at http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/project_iss... (lines 224-227).
We're now putting the uid of the person the issue is assigned to, not authored by, in the list of uids which will eventually be potential email recipients.
There are some related changes in lines 277-283.
It looks to me like before this patch was committed, if you were subscribed to "my own issues" on a particular project, you got an email in any of the following cases:
1. You created the issue
2. You commented on the issue
3. You were assigned to the issue when a comment was created.
Now, it seems that 2 and 3 still happen, but #1 does not.
I'm about to head out now and don't have time to roll a patch, but let me know if I'm overlooking something here.
Comment #15
aclight commentedThe attached patch fixes the fact that the original creator of an issue was not getting email notifications of comments on an issue he created unless he had also commented on that same issue. This happens in the case where the user selects to receive "own issues" on the subscriptions page.
I'm marking this as critical because of the fact that this behavior is a regression and directly impacts users who primarily monitor the issue queues via email.
The patch also keeps the behavior of the user an issue is assigned to gets the email notification if the user is subscribed to the queue.
Comment #16
dwwNice detective work, thanks! Now, where's that patch? ;)
Comment #17
aclight commentedThe patch got eaten by the other issue, which probably hasn't been created yet, that sometimes causes attachments to not actually be submitted. I'm pretty sure I attached the patch.
But in any case, i'll upload it tonight when I get home.
Comment #18
GoofyX commentedNice catch aclight! I'm glad this has been found. Behavior confirmed as you explain in #260355: Timezone handling settings not saved (I only got the e-mail for the first comment and not the actual issue).
Comment #19
aclight commentedHopefully the patch will stick this time.
Comment #20
aclight commentedComment #21
dwwThanks! Reviewed, committed to DRUAPL-5--2 and HEAD, and deployed on d.o.
Comment #22
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.