Posted by mcload on April 9, 2009 at 3:37pm
Jump to:
| Project: | Simplenews |
| Version: | 6.x-1.x-dev |
| Component: | Usability |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I think an option to resend a newsletter would be very useful. There are many questions about this in the issue queue and as far as I know the only solution is editing the database.
Comments
#1
Not possible?
#2
Yes, would be nice send the same newsletter every week, for example.
I discover that I can embed views like:
<?php$output = views_embed_view('myview', 'block');
print $output;
?>
So the possibility to send the last articles, news or any other filtered content automatically every week would be wonderful!
#3
subscribing
i know having the ability to send a "sent" newsletter to a few extra emails would be extremely useful. I get asked to do this all the time. What ends up happening is all those extra people getting a "test" newsletter. Which is less then ideal.
#4
Subscribing — would be great if we could do this.
I'm also using embedded views and would like to send out the same email every week using a "resend" function.
#5
... or maybe Send a Copy — that way you can create a new issue, from a previous mailing.
#6
http://drupal.org/project/simplenews_scheduler - but that's still only for D5.
#7
Subscribing
#8
subscribing
#9
subscribing
I just realised this was a possible requirement for my site and wondered why it wasn't available.
#10
Subscribing
#11
Sending a newsletter is a one-way option.
If you decide to resend a newsletter with the same content to the same audience, this is spam.
If you want to resend a newsletter (with updated content) - in my opinion - you're sending a different newsletter. So: Please add a new one. You might want the copy function for that which should mark the new node unsent.
#936982: Clone of simplenews node that has been sent
A newsletter should - after the sending process - always display the content on sent state. So a "previous newsletter" history should display correct.
To sum up: There's no need to resend a newsletter.
Am i missing something?
#12
Hi Miro,
In my case I sent the newsletter and unfortunatelly it didn't got the simplenews-newsletter-* tpl.php files, then I had to troubleshoot why and send the newsletter again. So I needed to resend it. To do it I had to modify the database.
In that case I think it wasn't spam since the two newsletters had diferent content provided by tpl.php files. Anyway I don't think sending a newsletter twice to the same audience has to be considered spam, as the audience is subscribed to the newsletter, it's just a duplicated mail, isn't it?
Edgar.
#13
I strictly consider receiving the same mail content again (so enforcing me to read it again) as SPAM.
Note that an option to clone the newsletter would be perfectly fine for you to "resend" a second item.
I'll push that supporting code into cvs in a few minutes.
Reworking template files seems a development issue case where i don't mind you needed to modify the database to find a workaround for your resend issue. For regular processes this should never happen as the template is (hopefully) no work-in-progress.
#14
@miro_dietiker I agree that receiving the same content twice is spam. In my use case however we send news releases to our media contacts with simplenews and we sometimes have mistakes happen and have to resend to make sure that our media contacts and subscribers have the accurate information. In this case this is NOT spam with content that is most times very similar except for a simple word change, because the only way to resend a newsletter is to update the database I have to set it and my content editors cannot. I dont see any reason to create a second node with almost the exact information in it and unpublish/delete the original node. An option to resend is a much more graceful solution in my opinion.
If this feature doesn't get added I will probably patch the module myself since it would greatly improve the module for my own use case.
#15
No activity in a long time. Closing. Please reopen if you still need this, in a more recent version of the module.
#16