The system emails me with the ads that have reached half-life on each notification run and there is no way to stop this (as far as I can see) other than deleting the ad. This means that I get emailed about the same ad all the time.
I can see that the module is trying to pick up all the half-life ads each time to get any new ones, but when there's only one ad, and none are being added by a user, it gets a little irritating to get email every few hours.
It would be nice to either have an ad be included in the list only once, to make the timeframe for the ads in the list have reached their half-life within the last 12 hours or that there be an option to select the notifications required (per user or sitewide) so that the notification can be disabled.
Thanks for your great work
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 0001-Issue-1441396-by-fgm-change-in-notification-frequenc.patch | 13.22 KB | fgm |
| #10 | 0001-Issue-1441396-by-fgm-change-in-notification-frequenc.patch | 13.22 KB | fgm |
| #9 | half_life_notifications_resent-1441396.patch | 7.3 KB | fgm |
Comments
Comment #1
fgmThis sounds indeed like a bug: the module should not pick the same ad more than once, and should only notify you once per event, for a total of 5 notifications (half life, expire minus one day, expire, purge minus one day, purge).
Did you find where the error was in its logic to build the list of new ads ?
Comment #2
LuRcH@www.daihatsu-drivers.co.uk commentedI've noticed this same problem in version 3.0-rc2 haven't been able to work out how to fix it though.
Comment #3
dejabobbi commentedI've been seeing the same thing. (Drupal 6.24, Classified Ads 6.x-3.0-rc2)
Also, I've been getting this error: "user notice: The classified_notifications_mail() function called token replacement with an array rather than a string for $text in /home/toymania/public_html/modules/token/token.module on line 263."
And then the emails sent out don't have the ad/url populated into them, just the spaceholder text. Is there something obvious I am missing on that?
Comment #4
ABQ Slim commentedI'm getting daily emails for Ad half-life. Using version 7.x-3.0-rc2.
Some of your Classified Ads on Roadrunner Region PCA have reached half their lifetime. They are listed below for your convenience.
Please visit your ads list at
http://www.roadrunner-region-pca.org/user/184/classified if you wish to modify them.
(147) 964 Rear Undertray
Comment #5
fgm@dejabobbi : the token issue is a different one. Opening new issue #1491880: Incorrect token generation and use for classified for it.
All: in order to reproduce the problem to fix it:
Comment #6
LuRcH@www.daihatsu-drivers.co.uk commentedThe problem for me only appears to be with the half life one, none of the others get sent out repeatedly.
Seems to happen regardless of how many ads are being notified.
Comment #7
fgmOK, so digging into it, there is one more issue: the tokens code backported from D7 just does not work as such. That's why D6 users don't get the ads list. Details in #1491880: Incorrect token generation and use for classified.
Comment #8
fgmAt this point, if you use the latest 6.x-3.x version, the only remaining problem on that list should be the repeating half-life message: no more warning, no more unreplaced tokens. Please check !
Comment #9
fgmHere is a test case catching the problem. Does it match what you observed, or does it need more test assertions ?
Comment #10
fgmActually, with even further checks, the module was operating as designed, sending up to one mail per 12 hours, to "push" users.
Since this seems to be undesired, I changed the logic so that no mail gets sent more than once on an untouched ad.
Comment #12
fgmOoops, patch is rolled against latest dev, not RC2.
Comment #14
LuRcH@www.daihatsu-drivers.co.uk commentedThe latest dev with the original half_life_notifications_resent-1441396.patch I can confirm didn't stop the repeat emails as you since worked out. I am now testing the latest dev with the 0001-Issue-1441396-by-fgm-change-in-notification-frequenc.patch in post #12
Comment #15
fgmLurch indeed: the initial patch only added the test to catch the error, but not the fix :-)
Comment #16
fgmCommitted to 7.x-3.x too. All should work on 6.3 and 7.3 now. Please review, and we can release the stable versions if you confirm the issue is fixed for you all when using the latest dev versions.
Comment #17
LuRcH@www.daihatsu-drivers.co.uk commentedAll appears to now be working as expected for me with the 6.x-3.x-dev version.
Comment #18
fgmOK, considering fixed, then.