I've looked for the SN Issues list and do not see any request for a feature that assumes that the subscriber is NOT logged in. These features are more for a "brochure-ware" site than an interactive portal site. So, I'd like to see a way to extend SN to do the following:

  1. Block Formsets:
    Create several subscription block formsets for various uses.
    1. Simple Subscribe (No User): Just the email address field. Used in a side-content or similar block. Does not create a full-fledged user. Assumes that user will never log in.
    2. Simple Subscribe (Adds User): Same as #1, but it adds the default fields required to create a new user ... or redirects to "Add User" page.
    3. Extended Subscribe Block (No User): Integrates with extended Profile and allows capture of additional data. Does not create a full-fledged user. Assumes that user will never log in. Fields might include:
      1. First Name
      2. Last Name
      3. Street Address
      4. City
      5. State
      6. Zip
      7. Email
      8. Basically, it would function like this:
        http://www.blowingrock.org/newsletter.html

    4. Extended Subscribe Block (Adds User): Same as #3, but it adds the default fields required to create a new user ... or redirects to "Add User" page.
  2. Add Value to SN Form Call:

    The following is the default SN form call:
    • <?php simplenews_subscription_manager() ?>

    Add an argument that would tell SN which block to display. Something like this:

    • <?php simplenews_subscription_manager('simple-no-user') ?>
    • <?php simplenews_subscription_manager('simple-add-user') ?>
    • <?php simplenews_subscription_manager('extended-no-user') ?>
    • <?php simplenews_subscription_manager('extended-add-user') ?>

Maybe this is already possible. I've looked around abut do not see it. I may be willing to sponsor this development.

Comments

apakuni’s picture

DOH! Homer Simpson moment.

The "Simple" elements exist when logged out. So, the only aspect needed would be the Extended.

Thanks Kitt!

frost’s picture

I would like to second the part of this request that is still relevent - an extended form which allows collection of more than just an email address. It would be really good to have optional fields such as name, phone, where you heard from us, etc.

dasjo’s picture

Version: 4.7.x-1.x-dev » 5.x-1.2

i'm looking for the extended subscribe block, too

Phillip Mc’s picture

I second that emotion for the ability to add fields like city/country etc. to the simplenews module.

jayp01’s picture

I too would like to see this feature for extended contact information incorporated into simplenews.

Designer Dude’s picture

anyone worked out a way to extend the form to include city/country?

debonator’s picture

Version: 5.x-1.2 » 6.x-1.0-beta3
Component: User interface » Usability

i'm going to hop on this request train. i would really like to be able to include the user's state. i run a voting website, and we'd like to send out reminders when deadlines are approaching. since this varies by state, it'd be ideal to send targeted emails.

sutharsan’s picture

Version: 6.x-1.0-beta3 » 7.x-1.x-dev
Component: Usability » Miscellaneous

Development of a flexible feature like this takes time or money. Anyone who want this feature developed can hire me (the module maintainer) at: Link3 Webdevelopment.

nimzie’s picture

I am quite interested in being able to collect a name with my email addresses/simplenews.

I have contacted sutharsan. Am not sure the kind of $ we're talking, but I am interested in helping grow this module and having this kind of feature set for the newsletter block. For anonymous users, an email without a name is so impersonal when it comes to interacting with the user again via the newsletter itself.

Has anyone had any success extending this block?

http://www.freelancewebdeveloper.net.au/node/325

I found this article, however there are some things missing that I can't figure out with my limited php knowledge. I think for the most part, they've got it - but there are some param issues with the simplenews_subscribe_user function reimplementation. With the addition of a new param, I don't know how to show that in the function declaration.

Is this close to helping anyone else with this issue?

callison’s picture

It seems to me that this would be best accomplished as a separate module that "extends" simplenews functionality. The resulting module could then be as flexible as you would want it (i.e. user-defined fields that could be generated into the subscribe form ... or whatever).

nimzie’s picture

I did some asking around and got a quote which was a show stopper for me.
I will have to find another way to do what I was trying to do :)

callison’s picture

sutharsan’s picture

Status: Active » Closed (duplicate)