Initial commit on new fork
Removed Sublime project files
Moved cron job into api call
*ISO the mysql recurr create and start date so that they don't get erased
*when processing pending contributions, update status to 5 (In Progress)
*add a method to retrieve previous contributions from same recurring so that we can copy source, page id and other useful info
*while processing recurring contribution set receive date with current time
*updating reccuring contribution start creation and modification date
*fix php bug integer limit
Made code compliant with 4.4 (MessageTemplate, next_sched_contribution_date)
Captured the eWAY Transaction Number in the Contribution
Added update_recurring_contribution() to standardise update logic
 - if the number of instalments is limited, and the next instalment date would
   be beyond the date of the last instalment, then Complete the Recurring
   Transaction, and set its end date
Changed complete_contribution() to capture eWAY Transaction Number
Added more defines for Contribution Status
Update compatibility version number to 4.4
Bootstrap CMS (to get access to mail tokens)
Correct hardcoding for Payment Processor Id
Correct PHP casting error for managed_customer_id
Add email parameters
Merge remote-tracking branch 'vincemd/master'

Conflicts:
	org.civicrm.ewayrecurring/process_recurring_eway_payments.php
Get receipt text from Contribution Page.
Set Non-Deductible Amount
Minor fixes
A number of improvements ...
 - Added support for all frequencies, eg 2 weeks, 3 months, etc
 - Removed hardcoding of Payment Processor Id
 - Removed hardcoding of Contribution Status
 - The eWAY gateway is determined from the payment processor id in the Recurring Contribution
 - The Net Amount and Invoice Id columns are now set in Contributions
 - Now guarantee to get the first Contribution in get_first_contribution_from_recurring()
 - Since @VinceMD added logic to make Recurring Contributions 'In Progress' I rewrote
   get_pending_recurring_contributions() to search for Recurring Contributions that are
   Pending for this Payment Processor, and then find the linked Contribution. Seems a more
   natural logic.
 - Since @VinceMD added logic to make Recurring Contributions 'In Progress' I rewrote
   get_scheduled_contributions() to search for Recurring Contributions that are
   'In Progress' for this Payment Processor, and then find the linked Contribution. More
   robust if Recurring Contributions are in various states.
 - Since @VinceMD changed the created_date logic to set the time, it no longer makes sense in
   get_scheduled_contributions() to check for an existing Contribution when that check only
   searches by date and not time.
 - Changed the logic in update_recurring_contribution() that marks a Recurring Contribution
   as 'Complete'. Now, if there is a limit to the number of instalments, it counts the number
   of Contributions, and Completes the Recurring Contribution if that count has been filled.
Send an email when the recurring contribution is submitted, so the donor doesn't need to wait for the batch to run before they get some sort of confirmation
Add support for cancelling and updating recurring transaction details
Add links to cancel/update URLs in receipt email
Set 'JobDesc' to '' since 'description' prevented editing of token customer by eWAY
Update README.md to be more specific about what hardcoding is needed, and to remove assumption that processing is monthly
Updated version in XML file
Merge my changes with ChrisC's
Tell potential users they need to set up a CiviCRM Job