Once you send a simplenews newsletter, is it possible to resend it again?

I don't see any way to do that but i'd like to be able to if possible.

thanks

Comments

sepeck’s picture

You can edit the database where it is marked as sent and change the value so that it will appear 'unsent'. Then resend it that way.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

newdru’s picture

i gathered that.. but setting up a site for someone else, that would not be a best solution..

i'm wondering if i could use nodeapi to add this setting to module without having to hack the module. doing it this way would allow it to be reused easier versus having to patch the module everytime it updates.

sepeck’s picture

OOooOOoooo, you had unstated assumptions with your requirements :D

I think there is a feature request in the SimpleNews issue queue for it, or at least we had a similar conversation on the forums about 6-9 months ago. You should check. I don't know off the top of my head how you could determine the stuff automatically to do it with a sql query.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

newdru’s picture

actually, it doesn't seem like it would be too hard does it?

you simply create a button called resend (instead of the dimmed out sent) if the sent column is checked in the db right?

that button has a callback that simply resends.. in fact, it could use the same function that initially did the send??

i'll take a look at this later when i have more time unless someone wants to beat me too it.

tunesmith’s picture

It's simplenews_newsletters.s_status - reset it from '2' to '0'.

(I don't know what '1' is.)

sepeck’s picture

1 is sending.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

esllou’s picture

as far as I understand it:

0 - don't send
1 - send on next cron
2 - already sent.

sepeck’s picture

1 - continue sending on next cron until all done. It only sends per the set limit each cron run.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

adidaniel’s picture

What is this?Where can i find the status?

gggdrpl’s picture

Hi everyone! I had the same question this post is about and I've found that if you edit a newsletter once it has been sent and check the box for "Create new revision" under "Publishing options" Drupal places the newsletter issue in the "Drafts" section once again, where you can edit it and resend the same content as a test or as a definitive delivery.

It seems you can repeat this procedure as many times as you want. At least I've done it twice and it worked out fine!

Hope this helps!

newdru’s picture

thanks for the post. i made the original post months ago and am just getting back to this issue so your input came at a very opportune time.

petya_vulcheva’s picture

Hi just to say that I tried this, but it didn't work to me. Actually the newsletter is not placed under "Drafts". Are there any other settings to do so?

gggdrpl’s picture

Hi
After you've sent a newsletter, it is placed under Sent Issues tab. If you edit any newsletter issue from that section, check the box for "Create new revision" and submit the form. That's when the issue is put back under the Drafts tab and you can manage it again as an unsent issue. That's how I did it!

pcambra’s picture

This didn't work for me neither :S

I have to update the status of the newsletter for being able to send it again.

ratnesh aarohi’s picture

I use the drupal clone module to make a clone of the exsisting newsletter - which is automatically saved in the draft folder. You will need to change the subjexct - becasue that will read as "clone of ..."

http://drupal.org/project/node_clone

Jorkkeri’s picture

One (really ugly way) to enable resending is to disable sent newsletter check from send newsletter-options part in simplenews.module file.
This enables same "send newsletter" options for already sent newsletters as new items would have instead of giving grayed out "newsletter has been sent" checkbox.

It works with simplenews statistics, too. It pretty much just saves modifications made in your existing newsletter instead of creating a new revision. So if you have any links in your newsletters you're gonna keep track of with statistics it records them all. You can even modify links in resent items and they show up in click statistics.

As stated, this method doesn't create new revision for newsletter item so if you edit contents after sending it you just get newest version of sent newsletter in "sent" folder. So if you wanna keep track of all versions of sent newsletters this "solution" isn't for you.

For not so programming savvy user just change this line

if (!isset($simplenews_values['s_status']) || (isset($simplenews_values['s_status']) && $simplenews_values['s_status'] == SIMPLENEWS_STATUS_SEND_NOT)) {

to this

if (TRUE){

in simplenews/simplenews.module-file
It should be close to line 560 or so..

For more programming oriented users you naturally should remove if else-sentences and tune up the solution for a bit but you most likely know what to do anyways so..

For more elegant fix you could show "Resend newsletter" button in "send newsletter"-part when newsletter has already been sent and create new revision of newsletter when being resent but I'm kinda out of time for now so sorry for this sh*tty fix.

I'll try to squeeze some time to do this properly in near future but for now you can just go with this to get things working temporarily.

SolasArd’s picture

we could also just change SIMPLENEWS_STATUS_SEND_READY status value from 2 to 0 at the very beginning of the simplenews/simplenews.module file

lines 39-41:

/**
 * NEWSLETTER SENT STATUS
 */
define('SIMPLENEWS_STATUS_SEND_NOT', 0);
define('SIMPLENEWS_STATUS_SEND_PENDING', 1);
define('SIMPLENEWS_STATUS_SEND_READY', 2); 

- replacing 2 with 0 here lets resend the same newsletter issue from the Drafts folder as many times as necessary.

benone’s picture

SUBSCRIBE.

Are you going to add re-send feature to stable version of module ?

THaks. SImpleNews is really handy and with MimeMail looks great in the inbox.

Lowell’s picture

It looks like this is where I can change the status, but it doesn't seem to work quite the same

field_data_simplenews_issue_status.simplenews_issue_status_value

setting value=1 looks like it tries to resend but sent nothing
and value=0 does not reset ui to enable resending

armyofda12mnkeys’s picture

It would be great to add a resend button, but also with a checkbox that says 'Send to new subscribers only' (maybe checked by default)...

Use case:
I helped setup a newsletter for someone in Marketing... then they set it out to their 100 subscribers (a 'welcome to our site' newsletter email)... now 15m later they said they have 5 more users, and possibly 5 more every day for the next few months, etc. It would be great to just resend, without the need to create a new Simplenews letter and add only those users to it each week (Kinda a pain for me or them).
or me just resetting the status to 0, which would re-send it to everyone when they click Send, which is undesirable ...
There should be a table that stores if they got emailed this SimpleNews node and pay attention to that setting via future checkbox/Re-Send button that I speak of.

creact’s picture

Looking for the same feature. Any update on this?

monstrfolk’s picture

See https://www.drupal.org/node/2854744 for a patch to resend emails.