Hi Jason!
Because Subscribe2 is designed to allow use of the BCC header to send the notification emails it is counter-intuitive and would cause many support issues having a keyword to insert an un-subscribe link.
I recommend adding a link to the Subscribe page that I recommend is written in the installation instructions. This can be linking using some keywords, for example in my email templates I have the following:
To change your settings or unsubscribe visit <a href="{BLOGLINK}/subscriptions/">{BLOGLINK}/subscriptions/</a>.
I’ve been thinking about this more, and am wondering if my initial request was unclear, because I’m having trouble understanding how your response relates.
Your suggestion for including that link using {BLOGLINK} makes perfect sense for most single site installations. Unfortunately, we’re using it in multisite, where each site owner is able to customize their own site as well as email templates. Getting each of these users to create a /subscriptions/ page, and then modify their email template to include a link to said page is basically impossible. 🙁
My suggestion (which I’ll probably have to try to figure out how to do myself if you don’t think this should be rolled into the plugin) is something like this:
I’ll use a hook to automatically append the following text to each outgoing email:
To change your settings or unsubscribe visit {BLOGLINK}/subscriptions/.
Then, I’ll need to create a rewrite rule that looks for the /s2-subscriptions/ and has unsubscribe form on it.
Does that, by chance, make any more sense than my original post?
Cheers!
@jason,
{BLOGLINK} should still work on a per site basis, the issue is going to be finding the right page on that sub-site.
Perhaps you could make use of the ‘s2_email_template’ filter and still make use of that keyword by adding a sentence with a plugin using that filter to all templates on your site (network activate the plugin you write).
Add a filter to the above hook, take the current template and add a string to it saying something like:
Your received this email from {BLOGLINK}. To unsubscribe or change you setting please visit our site.
> the issue is going to be finding the right page on that sub-site.
Exactly. The problem though, is that not every site uses the widget, or has easy links on how to unsubscribe once you arrive at the site. This is why I’m really hoping/pushing for the SAME /page-type-slug-url-thing/ on every site that I could use.
Thanks, as usual, for the lightning fast response 🙂
@jason,
IF (and it’s a big IF) you can get a consistent page slug name on all sites where this is active then you can just tag that slug to the end of the {BLOGLINK}.
I guess you could create a hidden page on all sites where Subscribe2 is active with a slug defined by you, and use that leaving all existing pages and widgets alone.
Yeah – definitely can’t get that consistent page across all sites, so creating said hidden ‘page’ is exactly what I’m trying to do.
I’ll give it a shot and let you know how it goes. Adding a ‘page’ at /foo/ should be trivial – but displaying and processing the unsubscribe form sounds a bit harder 🙂
Cheers
@jason,
When you create to /foo/ page place the Subscribe2 shortcode on there, you could also consider added the hide=”subscribe2″ parameter to make it an unsubscribe only form. That should work pretty well in most cases.
