First: +1 on this great module. You've done a great job of putting together a very usable module.

I like the block for subscription, including the RSS feed directly as well. However, rather than having all newsletter subscriptions in one block, I would like each newsletter to generate it's own block. That way, you could place different newsletter subscription blocks on different pages. The all-in-one block is not particularly useful, and also seems a bit broken: if I hit "subscribe" which of the multiple newsletters am I subscribing to? As an anonymous user, the links don't seem to be listed, but there is still a subscribe field.

Look at aggregator or quotes module to see how blocks are generated on the fly.

Comments

DriesK’s picture

DriesK commented

Just a very quick reply for now (I'm at work, I will reply more extensively later today): To list the links for anonymous users, you should set the "view links in block" permission for anonymous users in the access control panel.

boris mann’s picture

boris mann commented

There are multiple newsletters listed, but only one subscribe options -- am I subscribing to *all* newsletters that way? The subscribe box still shows, even if the "view links" is off for anonymous users.

DriesK’s picture

DriesK commented

The all-in-one block is not particularly useful, and also seems a bit broken: if I hit "subscribe" which of the multiple newsletters am I subscribing to? As an anonymous user, the links don't seem to be listed, but there is still a subscribe field.

The block is not broken, see my previous comment. However, I agree that the block is not very useful right now. For the moment, subscription is "all or nothing". When you subscribe, you automatically subscribe to all newsletters. This is, by the way, completely independent of which links are displayed... You can display no links, 1 link or 10 links, you're always subscribed to all newsletters available. I'm planning to change this asap, probably by the end of the weekend (as I described in this issue). This would involve 1 extra db table (e.g. sn_tid_snid).

However, how to implement this?

1. As borismann suggests, 1 block per term. I think this would complicate matters, since I also want to provide the possibility of turning off all blocks and create a custom subscription page, thereby rendering the subscription form by 1 single function call, and displaying links to newsletter information by 1 function call, as discussed here. This subscription form should then look something like this.

2. My suggestion therefore would be to define only 2 blocks for Simplenews module. One block would show the subscription form, and an admin would be able to decide which checkboxes are displayed (e.g. when a newsletter is discontinued, but published newsletters are still available on the website, subscription to certain newsletters can be disabled that way). A second block would show information about the published (on-site, not necessarily sent) newsletters: this could be a link to a taxonomy overview page, a link to an rss-feed, or the x latest newsletters' titles. All of this has to be configurable.

However, this would have an impact on other Simplenews functions as well. Here are some questions that just come across right now:

* The subscription list should then show to which newsletters users are subscribed. So, should an admin also be able to change these subscriptions? I think he should.

* The 'import subscriptions' tab should have checkboxes to enable an admin to choose to which newsletters users are subscribed when he imports them.

* The same goes for exporting users...

Any thoughts on all this?

boris mann’s picture

boris mann commented

I know that I would always want the ability to have one block per newsletter, as well as the central spot where a user can manage all their newsletter subscriptions. This does not conflict with turning off blocks -- you would enable a subscription block per newsletter, and then site admins can use block configuration to determine where it displays. Again, look at aggregator for how blocks are enabled/created on a per-feed basis for an example.

Your #2 option sounds complicated, and has too much information: both blocks don't sound like something I would want enabled.

For your questions, yes and +1 to all three.

DriesK’s picture

DriesK commented
Status: Active » Closed (duplicate)

Please post any further comments in this issue.