Hi all,
I think this module is simply wonderful and it can easyly become a full-featured newsletter system. But I think it should be more flexible...

I would like, in fact, to be able to choose to display all the registration fields into the subscribing-block, as well as maintaining them on a separate page (just like it happens now).

And I would like, also, to choose between having one subscription block/page for each newsletter and having an unique registration block/page for all the newsletters.

Finally, I would like to order all the fields by weight, and I think it is not possible now with the "personal info" fields, that are not displayed under the tab "manage fields" (in the subscribers tab).

These are my thoughts; what about you?

I am not able, at this time, to write a patch to implement these features; but, if needed, I could manage to create a testing-enviromment to apply the proposed patches (I have to learn how to do this! :-)).

Sorry for my bad English, I hope you could understand the text in this message...
If you need more clarifications/details, please do not esitate to ask for... ;)

Comments

ParisLiakos’s picture

ParisLiakos commented

yes,you are right:)
damn, i should think already for the weight thing:/
its ok,it will take some time for me too,though but i have time to keep this developing.

about the block per list,sounds good too,but i guess it would make more sense to just create a webform component and let everyone build whatever block they like:).
so +1 for the weight,but the block per list will go into the webform component effort:)

falcon03’s picture

falcon03 commented

Hi rootatwc,
creating a block per newsletter using a webform component should be ok, but it would be great to manage the personal-info of the subscribers (name, last name, etc) through the newsletter' interface and not through the web form' interface…
And if I add a new field to a specific-block, I would like to manage the data available from that field in my newsletter-subscribers details, as well as use them as tokens in my newsletter template…
Using web form to create a specific component for newsletter, how can we ensure to maintain this flexibility?
I have to add that a module called web form tokens exists, but I haven't tried it yet and I have no idea about the availability of a D7 version...

falcon03’s picture

falcon03 commented

adding to #2: I forgot to say, what about permissions?
A typical use-case would be, for instance, a site that has a newsletter that anonymous users can subscribe to and a newsletter that can b subscribed only from users that belongs to a certain role…

ParisLiakos’s picture

ParisLiakos commented

you are right...all these things must be taken into consideration..and permissions definitely makes this harder.
I will try to come up with a flexible solution during these days

mrfelton’s picture

mrfelton commented

I think all the ideas in this thread are a good idea. However, when it comes the the issue of multiple/configurable blocks per newsletter (which is my most wanted feature) I'm not convinced about the idea of integrating with webform.

How about instead, creating a Bean plugin.

There are a lot of links on the Bean project page that describe how to do this. I think this would be able to provide the most flexible and configurable block system, as Bean simply rocks!

mrfelton’s picture

mrfelton commented

Here is a good example of a bean plugin that allows users to build new blocks that tie into the twitter_pull module - http://drupal.org/project/bean_twitter_pull

ParisLiakos’s picture

ParisLiakos commented

hmm Bean looks nice,didnt know it..i will have to check it more:)

itserich’s picture

itserich commented

For Roles, I would like to be able to send a custom Newsletter to every user with a Role.

This should already be possible using other methods, but Newsletter is the easiest and most certain way I have found to send HTML formatted text e-mail.

For those of us who don't understand all the aspects involved in sending HTML e-mail, Newsletter is a real important tool. Thank you.

falcon03’s picture

falcon03 commented

In reply to #7:

I was wondering: why couldn't we just use a block as simplenews does?

So we won't have further dependencies!

ParisLiakos’s picture

ParisLiakos commented

We need #1498538: Move first name, last name, gender to fields fixed.Then users wont have to enter any field for the basic subscription to work.and will allow greater flexibility in the manage subscriptions forms like:

Finally, I would like to order all the fields by weight, and I think it is not possible now with the "personal info" fields, that are not displayed under the tab "manage fields" (in the subscribers tab).

i also like the idea of not introducing new dependencies,at least for 7.x-1.x

falcon03’s picture

falcon03 commented

Well, so let's work on the other issue first; this feature is very important for me and as I told in a comment to the other issue I would like to help...or at least to try to help! :-)

ParisLiakos’s picture

ParisLiakos commented
Version: 7.x-1.x-dev » 7.x-2.x-dev