Add subscibe blocks for each list that can be enabled and placed in the sidbar
ChrisBryant - March 24, 2009 - 06:52
| Project: | MailChimp |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
The primary use case would be to just have a similar version of the "http://example.com/mailchimp/subscribe" page but available as a block that can be placed anywhere. The second use case would be to have a separate block available for each list. Thanks.
#1
Subscribe. I would like to do this as well.
#2
+1. This would be very useful and much appreciated.
#3
+1 - subscribe blocks per list could be placed in a variety of regions.
#4
This would be really useful. I also need this and I'm willing to help in implementation.
Personally I think most list management should be done in a block instead of user profile. It's nice to have this information also in user profiles for registered users, but even more important to have newsletter information visible on any page site administrators want it to be.
#5
+1 I would LOVE to have this feature, also
Connie
#6
+1 to have this feature as well
#7
I saw a need for this and actually added a patch for this over in #482678 but I'll add it here and mark that one as a duplicate.
I haven't exactly met the requirements you guys have requested, but at least it's a start. Please review the patch and let me know what you think!
#8
Am I using this patch right?
I added the patch to the mailchimp source, now a block shows up in the blocks menu and I can add it to the home page, but basically what I get is a blank/hidden form:
MailChimp
what is wrong?
#9
The patch in #7 is missing the mailchimp_subscribe_form function (the patch only includes the block hook, not the function that actually creates the form).
If you're going to implement something, take a good look at the simplenews signup block. It's flexible, and you should be able to reuse a lot of code from it.
#10
Implemented in 6.x-2.x
#11
Automatically closed -- issue fixed for 2 weeks with no activity.