=== Subscribe2 === == Licence == Released under the terms of the GNU General Public License. Distributed with no warranty. Use it at your own risk. Version 2.2.3 to 2.2.12 by Matthew Robinson based on: Version 2.2.2 copyright (c) 2004 Scott Merrill (http://skippy.net/) == Version History == Version 2.2.12 by Matthew Robinson + Fix for missing Quicktags (probably since version 2.2.10) + Fix for occasional email issue where excerpts are incomplete Version 2.2.11 by Matthew Robinson + Fixed bug that would cause all subscribers to get digest emails + Added Select All check box to category listing Version 2.2.10 by Matthew Robinson + Improved sign up process by double checking email address + Fix for submenu issues encountered in WP 2.0.6 Version 2.2.9 by Matthew Robinson + Fixed get_userdata call issue + Added CSV export + Reworked options storage routines Version 2.2.8 by Matthew Robinson + Fixed missing line return in email headers that was causing failed emails + Added user feedback messages to profile area + Added ÔAuthornameÕ to the list of message substitutions in email messages + Fixed name and email substitution in Digest Mails + Fixed stripslashes issue in email subjects + Added new ÔActionÕ token for confirmation emails Version 2.2.7 by Matthew Robinson + Link to post in HTML emails is now functional + Fixed bug in Bulk Management so it works when first loaded + Ability to auto subscribe newly registering users + Added additional email header information Version 2.2.6 by Matthew Robinson + Fixed email headers to comply with RFC2822 standard (after breaking them in the first place) + Impoved XHTML compliance of user feedback messages and subscription form when presented on a blog + Tidied up presentation of the code a little + Cached some additional variables Version 2.2.5 by Matthew Robinson + Added functionality to Bulk Manage registered users subscriptions Version 2.2.4 by Matthew Robinson + Added functionality to block user specified domains from public subscription Version 2.2.3 by Matthew Robinson + Added functionality to allow for Subscribe2 Sidebar Widget + Added functionality to block public email subscriptins from domains defined under Options + Added functionality to send an email reminder to all unconfirmed public subscriber + Added removal of html entities (for example ©) from plaintext emails + Replaced spaces with tabs in Plugin format + Minor changes to admin layout to match WordPress admin function layout Version 2.2.2 By Scott Merrill, see http://www.skippy.net/blog/category/wordpress/plugins/subscribe2/ == Description == This plugin provides a comprehensive subscription management system for WordPress blogs. Visitors can subscribe and unsubscribe through a convenient web-based form. All requests require confirmation by email. Administators can configure the email template used for new post notifications, as well the messages used for (un)subscription requests. Admins can also subscribe or unsubscribe users, as well as send out an email to all confirmed subscribers. New in version 2.2, registered users of the blog can subscribe to individual categories! == INSTALLATION == 1) Copy buttonsnap.php into your /wp-content/plugins directory. 2) Copy the entire /subscribe2/ directory into your /wp-content/plugins/ directory. 3) Activate the plugin. 4) Click the "Options" admin menu link, and select "Subscribe2". 5) Configure the options to taste, including the email template and any categories which should be excluded from notification 6) Click the "Manage" admin menu link, and select "Subscribers". 7) Manually subscribe people as you see fit. 8) Create a WordPress Page (http://codex.wordpress.org/Pages) to display the subscription form. When creating the page, you may click the "S2" button on the QuickBar to automatically insert the subscribe2 token. Or, if you prefer, you may manually insert the subscribe2 token: This token will automatically be replaced by the subscription form, and will display all messages as necessary. == UPGRADING == If you are upgrading from any 2.1.x version of subscribe2, please delete both the /subscribe.php and /wp-content/plugins/subscribe2.php files before copying the new files into place. Your subscriber list will remain intact, and your options should be preserved. Create the WordPress Page as described above. == USAGE == Subscribe2 supports two classes of subscribers: the general public, and registered users of the blog. The general public may subscribe and unsubscribe. They will receive an email notification whenever a new post is made (unless that post is assigned to one of the excluded categories you defined). The general public will receive a plaintext email with an excerpt of the post: either the excerpt you created when making the post, the portion of text before a tag (if present), or the first 55 words of the post. Registered users of the blog can elect to receive email notifications for specific categories. The Users->Subscription menu item will allow them to select the delivery format (plaintext or HTML), amount of message (excerpt or full post), and the categories to which they want to subscribe. You, the blog owner, have the option (Options->Subscribe2) to allow registered users to subscribe to your excluded categories or not. When you post a new item, subscribe2 will generate (at least) one email for each of the following combinations of subscribers: * plaintext excerpt * plaintext full post * HTML full post So for each new post you make, you may receive up to three emails. *********************** ** AN IMPORTANT NOTE ** *********************** Some hosting providers place a restriction on the maximum number of recipients in any one email message. For example, the venerable Dreamhost (http://www.dreamhost.com/) does not allow any message to contain more than 30 recipients. Subscribe2 provides a facility to work around this restriction by sending batches of emails. To enable this feature, edit subscribe2.php in a text editor and go to line 36: define('DREAMHOST', FALSE); Change the "FALSE" to "TRUE" (without the quotation marks). Reminder: because subscribe2 places all recipients in BCC fields, and places the blog admin in the TO field, the blog admin will receive one email per batched delivery. So if you have 90 subscribers, the blog admin should receive three post notification emails, one for eah set of 30 BCC recipients. Batches will occur for each group of message as described above. A site on Dreamhost with many public and registered subscribers could conceivably generate a lot of email for your own inbox.