Merge pull request #1 from raamdev/000000-dev

* Check for custom template to override the default IP Restrictions 503 ...
A Few Improvements

- Updating Authorize.Net Form Generator to support max days of 365. See: WebSharks/Private#302
- Adding finishing touches to custom templates for IP Restriction errors. See: WebSharks/Private#148
- Fixing bug in `s2-cross-xml.php` for S3 Buckets. See: WebSharks/Private#321
Further Improvements

- Fixing bug in `s2-cross-xml.php` for S3 Buckets. See: WebSharks/Private#321
- Adding blurp about fuzzy translation entries in existing PO files that translate s2Member. See: WebSharks/Private#317
S3 Secret Access Key

- Adding note about Secret Access Key for S3 integration. See: WebSharks/Private#321
Bug Fix

- Fixing bug from recent addition in WebSharks/Private#148. Too many dirname() calls. Reducing this to two calls.
Bug Fix

- Fixing bug from recent addition in WebSharks/Private#148. Only processing custom templates when necessary; instead of on each restriction check.
Preparing Changelog For v130617

- See WebSharks/Private#325
Releasing v130617
MySQL Database (wait_timeout).

- s2Member now automatically increases the MySQL `wait_timeout` to `300` seconds during s2Member processing routines. Reason for increase: should any 3rd party service API result in unexpected connection timeouts (such as PayPal, Authorize.Net, Amazon, MailChimp, AWeber, etc); this may cause a delay that could potentially exceed the default `wait_timeout` of `30` seconds on the MySQL resource handle that is global to all of WordPress. Increasing `wait_timeout` before transaction processing will decrease the chance of failure after a timeout is exceeded. Among other things, this resolves an elusive bug where there are mysterious 404 errors after checkout under the right scenario (e.g. when an unexpected timeout occurs). This may also resolve problems associated w/ some mysterious reports where emails were not sent during s2Member's attempt to complete post-processing of a transaction (and/or where other portions of post-processing failed under rare circumstances). See also: WebSharks/Private#349
MySQL Database (wait_timeout).

- s2Member now automatically increases the MySQL `wait_timeout` to `300` seconds during s2Member processing routines. Reason for increase: should any 3rd party service API result in unexpected connection timeouts (such as PayPal, Authorize.Net, Amazon, MailChimp, AWeber, etc); this may cause a delay that could potentially exceed the default `wait_timeout` of `30` seconds on the MySQL resource handle that is global to all of WordPress. Increasing `wait_timeout` before transaction processing will decrease the chance of failure after a timeout is exceeded. Among other things, this resolves an elusive bug where there are mysterious 404 errors after checkout under the right scenario (e.g. when an unexpected timeout occurs). This may also resolve problems associated w/ some mysterious reports where emails were not sent during s2Member's attempt to complete post-processing of a transaction (and/or where other portions of post-processing failed under rare circumstances). See also: WebSharks/Private#349
MySQL Database (wait_timeout).

- s2Member now automatically increases the MySQL `wait_timeout` to `300` seconds during s2Member processing routines. Reason for increase: should any 3rd party service API result in unexpected connection timeouts (such as PayPal, Authorize.Net, Amazon, MailChimp, AWeber, etc); this may cause a delay that could potentially exceed the default `wait_timeout` of `30` seconds on the MySQL resource handle that is global to all of WordPress. Increasing `wait_timeout` before transaction processing will decrease the chance of failure after a timeout is exceeded. Among other things, this resolves an elusive bug where there are mysterious 404 errors after checkout under the right scenario (e.g. when an unexpected timeout occurs). This may also resolve problems associated w/ some mysterious reports where emails were not sent during s2Member's attempt to complete post-processing of a transaction (and/or where other portions of post-processing failed under rare circumstances). See also: WebSharks/Private#349
Updating Docs

- See WebSharks/Private#350
Merge pull request #2 from raamdev/000000-dev

* Exclude restricted pages from calls to wp_list_pages()
Updating Pro Form Shortcodes

- See WebSharks/Private#403
- This commit also includes a bug fix outlined in WebSharks/Private#387
Merge remote-tracking branch 'origin/000000-dev' into 000000-dev
Adding "pages" to Alternative View Options

- See WebSharks/Private#300
Adding Support for 0.00 Transactions/Coupons

- See WebSharks/Private#403
- Updating internal documentation.
- Updating routines to support 100% off against specific amounts.
- Updating routines to support rrt="", even when there is no underlying subscription (e.g. when 100% free).
- Updating routines to support rr="0" with a fixed term, where there is no underlying subscription (e.g. when 100% free).
- Updating IPN handler.
- Updating Pro Form generators.
- Updating Pro Form Shortcode handlers.
- Updating JavaScript routines for all Pro Forms.
- Updating Pro Form validators.
- Updating Return Page handlers.
- Updating tracking handlers.
- Updating API Notifications.
Resolved Slow Query & Pagination Issue

- See WebSharks/Private#418
Optimizing User Search Results Query

- See WebSharks/Private#418
Releasing s2Member® v130731

- See WebSharks/Private#430