["Part 2" of original issue summary]
When an issue has been sent, optionally allow to send an extra copy to specific recipients, in a very similar way to the existing 'test newsletter'. This is useful if a subscriber bounced and you fix the address or if you get bug reports about bad links and want to send yourself another test or if someone subscribes and tells you they would like a copy of the recent past newsletter.
"Part 1" of original issue summary was like this:
When an issue has been sent, optionally allow to go back and send the entire again. For example, this would make sense if the newsletter issue related to an event and the newsletter was used to send a reminder; if the event was altered or cancelled at the last minute then you would need to send again.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | simplenews.resending.3056037-interdiff-13-15.txt | 843 bytes | adamps |
| #15 | simplenews.resending.3056037-15.patch | 4.33 KB | adamps |
| #13 | simplenews.resending.3056037-interdiff-11-13.txt | 1.16 KB | adamps |
| #13 | simplenews.resending.3056037-13.patch | 3.39 KB | adamps |
| #11 | simplenews.resending.3056037-11.patch | 2.21 KB | adamps |
Comments
Comment #2
jonathanshawUse case #2 I can definitely see (and has no easy workround); #1 seems more of a stretch, and it's relatively simple (and usually better) to copy/paste/edit and send a new issue.
Comment #3
adamps commented@jonathanshaw #1 is directly relevant on a site we are building. The scenario is that issue entity is a content type that represents an event. A custom recipient handler calculates recipients based on event attendees (commerce order line items). Creating a new event is no good as it would not have the attendees and the duplication would be visible and confusing in the event calendar.
Comment #4
jonathanshawMakes sense ... I hadn't imagined the possibility of an issue entity that also served a very different purpose.
Comment #5
mrdrill commentedI too have a similar setup in Drupal 8 that requires the ability to resend. The Simplenews Status Reset module worked great for Drupal 7 but seems abandoned for Drupal 8. Any patch, work around etc to reset the status without having to delete and recreate the newsletter would be greatly appreciated.
Comment #6
adamps commentedYou can sort of hack around the restriction.
Make sure that revisions are enabled for your content type. Before sending, create a dummy final revision without any significant changes. Then after sending the newsletter, revert to the version before the dummy revision and you will be able to send again.
Comment #7
mrdrill commentedThank you for the workaround suggestions, appreciate the response.
Comment #8
bibliophileaxeI've added a small module to allow this: https://www.drupal.org/project/simplenews_resend
Comment #9
adamps commentedGreat thanks. I'll take a look when I get a chance (busy right now sorry).
Comment #10
adamps commentedFor part 1, the button should be named "Reset". It should likely reset the statistics. There is a very real danger of sending the same newsletter to the same people, which would tend to be called spam. So maybe it should only work if you reset the newsletter content at the same time?? At minimum there should be a clear warning of the dangers.
It seems to me that creating a new newsletter is not so hard. It has the advantage that you get a clear history of when you sent out newsletters and how many people it was sent to. So perhaps part 1 is better in the separate module rather than being here.
Edit: corrected wrong reference to part numbers
Comment #11
adamps commentedPatch for part 2
Comment #12
adamps commentedComment #13
adamps commentedComment #15
adamps commentedComment #16
adamps commentedComment #18
adamps commentedComment #20
ressaMaking the title more precise.