Subscribe2 HTML v10.15

Version 10.15 of the Subscribe2 HTML was released about four weeks ago and is available now. This version has been tested on WordPress 4.7.4 and 4.7.5 and 4.8. It requires at least WordPress 3.3.

Current users of Subscribe2 HTML with an active support and upgrade subscription can upgrade using the WordPress plugin admin page.

Version 10.15 contains the enhancements and bug fixes listed below.

  • Introduced a more robust way of collecting remote IP addresses for logging subscription requests in PHP4
  • Introduced a method for updating for IP address using client side javascript – useful when site pages are cached
  • Improved Accessibility for Subscribe2 menus in keeping with planned changes for WordPress 4.8
  • Dropped legacy use of screen icons for admin pages to allowed continued compatibility with older WordPress versions
  • Correct capitalisation of the Return-Path email header – props Kyle Johnson
  • Introduced a feature to allow preview email to be sent while editing content, even in draft status – suggested by silverback
  • Other minor bug fixes and enhancements
  • Tested on WordPress 4.7.4, 4.7.5 and 4.8
Advertisements

Subscribe2 HTML v10.14

Version 10.14 of the Subscribe2 HTML was released about four weeks ago and is available now. This version has been tested on WordPress 4.7.2 and 4.7.3. It requires at least WordPress 3.3.

Current users of Subscribe2 HTML with an active support and upgrade subscription can upgrade using the WordPress plugin admin page.

Version 10.14 contains the enhancements and bug fixes listed below.

  • Fixed display of update messages on the Plugins page
  • Added setting to allow display of Registered Subscriber form on the front end
  • Make ‘Sender’ error notice on Subscribe2->Settings page dismissable
  • Add security measures to AJAX form
  • Further improvements to code layout and file naming using WordPress Code Sniffer Coding Standards
  • Tested on WordPress 4.7.2 and 4.7.3

Subscribe2 HTML v10.13

Version 10.13 of the Subscribe2 HTML was released about two weeks ago and is available now. This version has been tested on WordPress 4.6.1 and 4.7. It requires at least WordPress 3.3.

Current users of Subscribe2 HTML with an active support and upgrade subscription can upgrade using the WordPress plugin admin page.

Version 10.13 contains the enhancements and bug fixes listed below.

  • Abstracted the code for the ‘Your Subscriptions’ page to allow placement elsewhere – props Göran Rudling
  • Improved compatibility and efficiency of CSS embedding functions – thanks to L Sterling
  • Added single and plural alert message when deleting subscribers
  • Fixed file name error with Ajax form JavaScript library
  • Link initiation of plugin to WordPress hook to avoid issues with pluggable.php being called – thanks to @sneezry
  • Updated links to the new plugin website
  • Fixed an SQL bug in the automatic cleaner function for unconfirmed subscription requests
  • Extended use of custom stylesheet filter
  • Improve initialisation of some early filters – thanks to Jeff
  • Ensured central position of the popup AJAX form
  • Add check to fail gracefully when processing a ‘post’ with no category assigned at the time of publication – props @flymike
  • Tested on WordPress 4.7

Subscribe2 HTML v10.10

Version 10.10 of the Subscribe2 HTML in now available. This version has been tested on WordPress 4.4 and 4.4.1. It requires at least WordPress 3.3.

Current users of Subscribe2 HTML with an active support and upgrade subscription and upgrade using the WordPress plugin admin page.

Version 10.10 contains the enhancements and bug fixes listed below.

  • Added automated reminder emails sent 2 days after initial sign up request, interval can be changed via filter, or disabled
  • Code layout enhancements and inline documentation improvements
  • Improvements to comment form subscription checkbox / user messages
  • Enhanced ‘Cleaner’ task to ensure address toggles by admin are not immediately deleted by the task
  • Enhance ‘toggle’ and ‘delete’ functions to limit action to a single database entry
  • Improved wildcard implementation for barred domains to block internationally similar domains e.g. yahoo.com and yahoo.co.uk with yahoo.*

Free version of Subscribe2 is back

It seems that the free version of Subscribe2 has been restored to the WordPress plugin repository and it is great to see it back! 🙂

Looking at the code differences it seems that, for the time being at least, the ReadyGraph code has been removed.

I thought readers of this blog may like to know about this, but as previously stated, I am no longer involved in the development or support of free version of Subscribe2.

Subscribe2 HTML still available

Over the last 10 days or so the free version of Subscribe2 has been offline while a security issue is being patched and user experience is improved. A patch has been submitted and is under review by the WordPress plugins team. In the meantime, I wanted to advise that Subscribe2 HTML is not affected by this issue and is still available for purchase.

Unsubscribe links in notification emails

UPDATE: Unsubscribe links have been implemented as a feature and are available now in version 10.7 of Subscribe2 HTML.


TL;DR – I’m thinking of adding a feature allowing unsubscription links in the notification email in the next version. I hope I’ve found a good implementation for this feature as it isn’t straightforward. What do you think? Comments please… 😉


For a long time the Roadmap for Subscribe2 has stated that unsubscribe links in the notification emails has been considered and dismissed as a development route.

Why? Well, for a few reasons:

  • Subscribe2 is designed to be able to send individual emails but it can also be configured to send a single email to multiple recipients via the email BCC header – so the unsubscribe link would not be individual to each recipient
  • Subscribe2 can send up to 4 email types and in 2 formats, HTML and plain text – formatting can get messy when trying to implement a solution for all email types
  • Subscribe2 supports two user type, Registered and Public – the latter can click on a link to delete their email address but Registered Subscribers need to log in to their profile and change their setting – so a single link isn’t enough

So, where are we at right now?

Well, I think I have a satisfactory and workable solution now that I can spend more time developing Subscribe2 HTML while Subscribe2 is looked after by the folks at ReadyGraph. (See here for more about that split).

Basically, I have implemented a new {KEYWORD} called {UNSUBLINK}. This keyword is replaced by an unsubscribe link for Public Subscribers and a link to the ‘Your Subscriptions’ admin page for Registered Subscribers. These links are very basic in their implementation to allow for the plain text emails.

So, to allow greater control over the final output in the email there are also API filters for both links that passes both the generated link and the email type. This allows individual sites to use a little code to add some text and formatting to the link depending on the link and the email type. So for example (see below) you can return a nice sentence to Registered Subscribers with a word linked to the ‘Your Subscriptions’ page.

function custom_public_unsublink( $link, $email_type ) {
	if ( 'text' === $email_type ) {
		return "To unsubscribe click here:\r\n" . $link;
	} else {
		return 'To unsubscribe click here:
<a href="' . $link . '">' . $link . '</a>';
	}
}
add_filter( 's2_unsublink_public', 'custom_public_unsublink', 10, 2 );

function custom_registered_unsublink( $link, $email_type ) {
	if ( 'text' === $email_type ) {
		return "You may manage your subscription options from your profile\r\n" . $link;
	} else {
		return sprintf( 'You may manage your subscription options from your <a href="%s">profile</a>', $link );
	}
}
add_filter( 's2_unsublink_registered', 'custom_registered_unsublink', 10, 2 );

Finally then, this is the best solution I can currently think of, but I’m happy to hear some feedback on this before I push this feature out. Comments are open so let’s have some constructive feedback please. [Off topic comments will be deleted!]