Newsletter lists

[p38]

Great new newsletetr upgrade to Phoca email, many thanks.

Is it possible to have newsletter lists?

eg: user can subscribe to various newsletters?

[x] Monthly Newsletter
[x] Club Newsletter


Then when you create a new newsletter, you simply say which list it belongs to, then you cna send email to that list.

If we have this, it will be a perfect newsletter facility.

Paul.

[Jan]

Hi, for now there is no such option.

I will add into feature request list.

Please let me know more information how this should work, my idea:

- in module - there should be added select box for different newsletter
- in backend of the component - there is a feature to have different newsletters, so the only one feature which should be added is column by users - where the newesletters will be listed

Jan

[p38]

Hi Jan, sorry about delay, I was expecting an email notification to say you have replied, so looks like it is not working.

You will need to add an extra field to the newsletter called "MailingList" or "Category" or "Newsletter List". This enables one to have multiple newsletters in a certain list. This mailing List can be setup in backend and will be available as a dropdown.

Then on the subscribers module, you have the name and email, but you add a list of checkboxes for each of the mailing lists.....

Code: Select all

Name .....................
Email......................

[x] Monthly Newsletter
[x] Club Newsletter
[x] Daily Newslettter

In this way, the subscriber can choose which newsletter list he wants to receive.

Now for sending newsletters, you choose the one you want to send. Because it has been assigned a MailingList, all you do is send it to all subscribers that have indicated they want to select this newsletter.

At the moment, your component sends a newsletter to ALL subscribers, and works if you only have one mailing list.

With this new way, I can have multiple mailing lists and choose how I send my newsletters.

I am willing to help you on some PHP dev and testing if you point me in the right direction. I have 2 sites I would like to use this component on, and am holding out hoping you would consider this request

I have shown you what phoca mail could look like in attached image.

Paul.

[Jan]

Hi, hmm, now this is a little bit complicated as there can be two ways:

a) to have new table for "lists"
table list must be in relation to newsletter and of course to users
newsletter can have only one list
user can be assigned to more lists

or
b) there will be no lists but newsletters will be directly assigned to users
user can be assigned to more newsletters.


In fact in b) you will simplify all this and you will not lose any features:

- in module, there will be listed newsletters
- user can be assigned to each newsletter
- when you send newsletter - it will be send to users who are assigned to newsletter

To understand it correctly, is there some reason to complicate the situation and have the lists? In fact all can be done without lists only with newsletters and you will not lose any feature - the goal - so each user gets only the newsletter where he/she is subscribed will be accomplished.

Instead of listing lists in module, you will list newsletters :Idea:


But of course there can be some reason to have the lists, if you know it please let me know so I can think about it.

Maybe:
- if you add new newsletter to your system, in fact such cannot be included for existing users

Jan

[p38]

Hi jan, I relaise the need to keep it simple.

Here is the scenario......

If I want to receive only newsletters sent each month, yet my friend wants to receive daily newsletters, how would this be achieved? I would like to subscribe only once, not every time there is a new newsletter?

Your method will only work if we use the same newsletter to change the conent each time, as you then keep it one newsletter for each scenario.

But the content of newsletters change each time a new one is sent out, so how would you propose to keep old newsletters for subscribers to refer back to them using the token?

One way is for you to save the newsletter in a history table when sent and this gets used for links instead of linking to the actual newsletter. In this way you keep a record of old newsletters. So all you need to do is make a new history table and an internal copy facility .

Paul.

[Jan]

Hi, I think, it will be easier to do the lists, I will take a look at it but seems that using the lists will be more logical

Jan

[p38]

Let me know how I can help you in any way with this.

Paul.

[Jan]

Hi, please test it:
https://www.phoca.cz/news/821-phoca-emai ... 1-released

- user can be assigned to more lists and the same for the newsletter - it can be assigned to more lists too.

Jan

[p38]

will thanks Jan, looking forward to it.

Paul

[Jan]

Ok