Posted by ejort on February 20, 2009 at 4:44am
Jump to:
| Project: | StreamSend Email Marketing |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
I was wondering what the future plans are for this module (is there a roadmap or TODO list somewhere)? We've recently committed to using StreamSend as a solution in all of our future sites and will need the functionality you've currently developed as well as some extra features. It's also possible that I'll be able to get some paid time to assist in the development of this module.
Cheers,
Eric
Comments
#1
I'm also interested in helping with this module. I will need it for many sites in the future and will have a little paid time to assist with the development as well. I'm kind of a newb when it comes to module development, but I know PHP fairly well and am familiar with the StreamSend API. I also know the StreamSend developers and the president of the company and work with them on a regular basis. I live in the same city as them. So I can talk with them directly, if the need arises.
Thanks,
Carson
#2
Hello,
I realize this post is a few months old, but I just wanted to say that I have converted this module to 5.x, added features and fix some of the bugs (and probably added a few more along the way). The version I have setup is working on our live site. I am currently working on upgrading my version of this module to 6.x. Once completed I will post the version I have been using.
Thanks,
Matt.
#3
Hello, I'm with StreamSend. I've sent an email to the administrator of this module request admin privileges. We'd like to fix any bugs that may exist with this release and to work with the community to add additional features. Figured I'd post here as well in case my email doesn't make it through.
Thank you.
#4
Dforootan,
I've been working on this module getting it good enough for our website for a little while now.
Here are of features that I've been working on that I think would be great additions to this module.
--Allow users to manage their lists from their profiles.
--Ubercart checkout pane intergeneration.
--Easy functions that add / remove people from lists. streamsend_manage(op, email, list) or something similar would be great.
--Multi-list signup.
Basically, Instead of just using one list, it would be great if we could present users with multiple lists on the various signup places on the website. I think there should also be a 'default' list set so that an admin can specify to either allow visitors to be presented with all of the lists or a simply email field that adds them to the default list.
--Email Generator
One thing that is pretty important to us is the ability to generate our emails on our site and then use the Streamsend email generator tool (not sure what its called off the top of my head) to import the email that we created. I set such a feature up but it is a hack job and would need to be completely redone before it could be released to the community.
I'm glad someone else has taken an interest in this module =).
Thanks,
Matt.
#5
Hi Matt,
Excellent! Is it possible for you to upload a patch file or a zip of your current module? We'll go through it on our side and port what we can over to the version we're fixing up.
I'm very interested to see how the email generator is working (even if it is a hack).
Thank you,
Dan
#6
Hello,
I've committed some updates for this module to CVS. Can anybody tell me what the protocol is for creating a new "release"? Should I do that now or let people download and test my updates through cvs? I'm new to Drupal, so if anybody wants to checkout the code any feed back is welcomed.
I've worked closely with StreamSend over the past several years, was a small part of the team that developed the current version of the application, and still work directly for StreamSend on a regular basis.
Thanks,
Brandon
Here is some information about the changes I just committed to cvs.
=============================================
Issues Fixed:
Not all StreamSend Accounts have an audience_id of 1. The module will now detect and locally store
the audience id for a given StreamSend Account once the API Login ID and Key are entered.
Cleaned up initial setup process to avoid curl errors showing up before the login id and key are
setup.
Features:
StreamSend Lists Integration:
Select any number of StreamSend lists for Drupal users to be members of. Each selected list
can be set to "pre-checked", "unchecked", or "automatic". For any lists set to "automatic" a new
user that signs up or a user that updates their profile will automatically become a member of
that list in StreamSend. If a list is set to "pre-checked" or "unchecked" those lists will
appear as checkboxes on the user's account edit form or the register form. If a user is new and
the list is set to "pre-checked" then the checkbox for that list will be "pre-checked" during
registration.
StreamSend Field Integration:
By default you can integrate the drupal users email address and login name with fields in
your StreamSend Audience. If you enable Drupal's "Profile" module, you will then be able to link
any of those user profile fields directly to a field in your StreamSend Audience.
Other Configuration Options:
Set the name of the form list section where the list checkboxes appear
Set the "#weight" of the form list section to move it up or down your user form
Set the Time To Live for the caching of list membership information locally
Set the "Profile" category where your StreamSend List form section appears
Performance Considerations:
StreamsSend person id is cached locally:
Since the Streamsend API requires knowledge of the unique id of a particular subscriber
in the StreamSend audience, these values are stored locally in the drupal database after the
first time they are retrieved for a given email address.
Individual User List membership is temporarily cached locally:
User list membership data is cached locally to enable a form to be rendered more than once
without having to make another trip to the StreamSend API. The length of time these records
are cached can be customized in the module configuration.
Unsubscribe Form:
Defines an "unsubscribe" node at the root of your drupal installation (/unsubscribe) where users
can enter their email address to change their StreamSend status to "unsubscribed" (Note this
was left in this module to be compatible with the previous development version of this module,
there is currently no way for a user to change their status back to "Active" without
editing their profile through StreamSend's subscriber interface.)
Module Install/Uninstall/Schema Hooks:
The module now has install, uninstall, and schema hooks defined. Note that uninstalling this
module has no effect on your StreamSend account. It simply removes all module settings and
module tables from your drupal database.
#7
I'm closing this thread. Please create a new thread with suggestions, etc.
Thank you.