Project:Simplenews
Version:6.x-1.0-rc6
Component:User interface
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

hey there,

I just think that dropping poormanscron altogether is not very nice on the end users.

from a newbie point of view, cron IS complicated. and what is the point of ever having a CMS if you have to figure out how to do all the dirty work? ;)

so what I propose is: a way to configure cron jobs from within simplenews. and, if possible, a way to coexist with poormanscron. whattyasay?

I'd love to help, if I could write some decent PHP. but I am available for testing.

oh, and how does simplenews work on a multisite environment?
let's say we have Site A as the main site, with poormanscron but not simplenews;
then site B as an addon site, without poormanscron but with simplenews.

would this work for update checking AND newsletter firing?

cheers,
Luciano

Comments

#1

subscribing

I like this idea, I do like poormanscron and would like to continue to use it if it was possible.

Edit: Ok, so this is a know bug in poormanscron.

#2

Status:active» closed (won't fix)

This should be solved in Poormanscron so other modules benefit too.

#3

Is this still problem in new version of Poormanscron D6 2.2?
Has anyone test it already?

br,
Gapa

#4

Category:feature request» support request
Status:closed (won't fix)» active

This issue #119094: Use drupal_cron_run() (fixes FeedAPI compatibility problem and multiple simultaneous runs) is closed, so it might be fixed. Please test and report back (we will love you ;) )
Changing status to keep track.

#5

Status:active» closed (fixed)

No activity, closing issue.

nobody click here