Closed (fixed)
Project:
Poormanscron
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
29 Jul 2004 at 09:42 UTC
Updated:
23 Aug 2005 at 01:12 UTC
Jump to comment: Most recent file
The aggregator module uses drupal_set_message in the _cron hook (indirectly), sites using cron.php probably wont notice this but on sites using the poormanscron module these messages will be shown to the user who invoked the _cron hook.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | poormanscron_1.patch | 1.28 KB | Uwe Hermann |
| #7 | poormanscron.module | 3.71 KB | Uwe Hermann |
| #5 | poormanscron.module.wipe_messages_0.patch | 1.43 KB | ejort |
| #4 | poormanscron.module.wipe_messages.patch | 1.37 KB | ejort |
Comments
Comment #1
Steven commentedIsn't this a poormanscron bug? The module should wipe the drupal messages when it's done.
Comment #2
bart jansens commentedPossibly, i wasnt sure if it was a poormanscron or aggregator bug :)
The problem with just wiping all messages is that any existing messages will be erased also.
We could just close the session before invoking the cron hook, i'll try that and see if it causes any other problems.
Comment #3
jsambrook commentedAny movement on this? I'm getting complaints from picky (!) users :)
Comment #4
ejort commentedHow about something like this patch? It retrieves the drupal messages before the cron run (without deleting them though, in case the cron run fails), then erases the entire set of messages and restores just the saved prior messages when the cron run finishes.
Cheers,
Eric
Comment #5
ejort commentedoops, it seems a spare 's' escaped from my keyboard and into that last patch. Don't worry though, I caught the thing and it's safely secured away now. This patch should actually work.
Cheers,
Eric
Comment #6
josef commentedThanks for the patch, Eric, it's really what i need! Unfortunately I get the following message:
I had a fresh copy of poormanscron.php. Is there any possibility you can look info your patch again?
Regards,
Josef
Comment #7
Uwe Hermann commentedHere's an updated patch which should apply to the CVS version of poormanscron. I'll commit the patch to CVS in a few minutes, an updated poormanscron tarball should be available for download in a few hours.
In case of problems, please report them here.
Uwe.
Comment #8
Uwe Hermann commentedOops, sorry, I posted the whole file, not the patch. Here's the correct one...
Comment #9
Uwe Hermann commentedMarking fixed. I applied the patch to CVS and 4.6.
Comment #10
josef commentedMarking fixed. I applied the patch to CVS and 4.6.
Does that mean it should work on the latest Poormanscron module (non-CVS)? I tried but got the following:
Good though you posted the whole module file, i just replaced the original one with the new one and it does the job!
Comment #11
josef commentedI take the last statement back, it doesn't syndicate new rss posts at all!
Comment #12
Uwe Hermann commentedWhat did you do? The downloadable version for Drupal 4.6 should be fine now, without any patching. Applying any patch to that is doomed to fail. Uwe.
Comment #13
josef commentedOh, it's just me and reading instructions, sorry. I guess it should work now then. Thanks for this great module, Uwe!
Comment #14
(not verified) commentedComment #15
Uwe Hermann commented