Page 1 of 1

[SOLVED] Newsletter Made Simple - Jobs

Posted: Mon Jul 28, 2008 3:07 am
by superwad
I'm testing out the NMS module with a sample set of 57 email address.  All email address are going to the same account (using the Gmail option of adding an extra period between any character to seem like a new email).  I have confirmed they all work (they all contain the same letters, just extra periods in different locations).

So I imported all the users to the same newsletter and create a new job.  I then process the job.  My settings are still default, so it tries to send messages out in batches of 50.  The batch processing window opens and starts processing emails.  My inbox, over the course of 5 minutes, slowly fills with 50 emails, but no more.  The batch window processed, and then simply stopped.  It didn't proceed with the remaining 7 emails, nor did it give me an error message.  Upon looking at the job status tab, my job is listed with an ERROR status, but won't give me any further clarification. 

This also happens if I send to less than 50 recipients, like 1 or 2.  The batch processing window will open, and sometimes will say it completed the run.  The job status tab still says the job had an ERROR, but no further detail is given.

Can somebody help me with this?  The processing needs to work for any number of recipients.

Thank you.

Re: Newsletter Made Simple - Jobs

Posted: Tue Jul 29, 2008 6:57 am
by superwad
I found the problem.  There was a error in the queue processing function causing a 30 second wait instead of a 30 microsecond wait.

Open: action.process_queue.php.
Find: line 430:

Code: Select all

sleep($this->GetPreference('between_batch_sleep',30));
Replace with:

Code: Select all

usleep($this->GetPreference('between_batch_sleep',30));
Works like a charm!

Re: [SOLVED] Newsletter Made Simple - Jobs

Posted: Tue Jul 29, 2008 1:07 pm
by calguy1000
Not a bug.... it's supposed to be in seconds.

Re: [SOLVED] Newsletter Made Simple - Jobs

Posted: Tue Jul 29, 2008 8:58 pm
by superwad
Well then I stand corrected.  In any case, the 30 second delay was causing the execution of my batches to die, so the change had the desired effect.