I would like to suggest having a new form page for subscription not just on the block. With this, we can add text and images to entice more users to subscribe.
I would like to suggest having a new form page for subscription not just on the block. With this, we can add text and images to entice more users to subscribe.
Comments
Comment #1
DriesK commentedInteresting thought. I'll consider it. Thanks for your input, it is greatly appreciated!
Comment #2
dries commentedI think that for quite a few people, the block won't cut it. They'll want to setup a page to accompany it. Like on drupal.org, we need (and have) a newsletter page too because we want (i) an explanation of what the newsletter is about (description, target audience, frequency of publication, contact information of editor), (ii) direct links to the public back issues, (iii) a subscription form, (iv) an image or two and (v) and maybe a privacy policy.
At the same time, I think it would be pretty hard for the simplenews module to generate a page that fits everyone's needs/expectations. Similarly, it is pretty hard to generate a block/page that fits everyone's needs/expectations. The solution? Provide a good default block that makes 75% of the users happy, and provide an API for us power users. Like that, we are able to craft our own newsletter page/block using a 'PHP code node' or 'PHP code block'. For example:
simplenews_subscription_form()-- returns a form that the user can use to subscribe/unsubscribe from the available newsletters.simplenew_recent_newsletters($tid, $count = 5)-- returns an itemized list that shows the $count last newsletters with term$tid. (Might already be available in taxonomy.module.)Ideally, the default simplenews block would also be able to re-use
simplenews_subscription_form()to render its form(s).Comment #3
DriesK commentedI think the best solution is a 2-block system as I described here. That way, all combinations are possible:
1. Subscriptions and newsletter info (link to page and/or rss and/or x latest titles) are managed through a block.
2. Subscriptions managed through a block, newsletter info by function call on custom page
3. Newsletter info in a block, subscription from rendered on a custom page
4. Both on a custom page, and no blocks
Comment #4
DriesK commentedPlease post any further comments in this issue.