- Version bump due to messed up version numbers in previous release.
- Use multi certificates with PaypalEncryptedPaymentsForm
- Fixed issue #166 - regression from 0.2.7 when using
- Django 1.11 compatibility.
- Added warnings for untested code.
- Fixed issue #147 - compatibility with Django 1.10
verifymethod of IPN/PDT so that it can be re-run in the case of a PayPal server error.
- Added ‘re-verify’ admin action for IPNs.
- Other IPN admin improvements.
- IMPORTANT: Removed the undocumented and untested
item_check_callableparameter from several IPN and PDT processing functions. You should implement checks in signal handlers like
valid_ipn_receivedor other calling code.
- Fixed issue #119 - flagged IPNs not excluded from duplicate checking.
- Fixed issue #126 - documented need to check amount received.
- Better handling of unknown datetime formats, thanks rebwok, PR #137
- Added pytz dependency
- Dropped support for Django 1.4 and 1.5.
- Fixed crasher with AmbiguousTimeError.
- Better logging for paypal.pro.
- Fixed Django 1.7/1.8 compat for EmailField.
- Added missing migration for PDT model.
- Added missing South migrations
- Fixed max_length of IPN/PDT
- Fixed issue #105 - IPN failure when running under non-English locale
- Added missing fields
- IMPORTANT: Deprecated the
PAYPAL_RECEIVER_EMAILsetting to allow multiple receiver emails in a single app. This has several consequences for your code, which must be fixed before upgrading to 0.4.x, when this setting will be dropped entirely:
- When creating a
PayPalPaymentsFormyou must provide the
businessfield in the
- Validation of
receiver_emailmust be done in your
valid_ipn_receivedsignal handler and your PDT processing view. Take into account the fact that the user can tamper with the form fields before posting them to PayPal.
- When creating a
- The use of the
pdtview for PDT payments is deprecated. Now you should provide your own view and use the
- Small fix to logging, thanks frankier
- Small fixes, including not depending on South.
- Fixed some
PayPalIPNDateTimeFields that were not being handled like the rest. Thanks thiagogds for the patch.
PayPalNVP.timestampfield so that it receives timezone-aware datetimes if you have
USE_TZ = True
Fixed timezone parsing of PalPal data so that
PayPalIPN.payment_dateand others are handled correctly (if you have
USE_TZ = True).
This does not include a migration to fix old data - see the release notes if you need that.
Work-arounds for bugs in the IPN Simulator
Other small fixes
Regarding the handling of dates: If you want to fix historic data in your IPN tables, you need to apply a migration like the following:
# -*- coding: utf-8 -*- from __future__ import unicode_literals import pytz from datetime import datetime from django.db import migrations from django.utils import timezone PAYPAL_DATE_FORMATS = [ "%H:%M:%S %b. %d, %Y PST", "%H:%M:%S %b. %d, %Y PDT", "%H:%M:%S %b %d, %Y PST", "%H:%M:%S %b %d, %Y PDT", ] def parse_date(datestring): for format in PAYPAL_DATE_FORMATS: try: return datetime.strptime(datestring, format) except (ValueError, TypeError): continue def fix_ipn_dates(apps, schema_editor): PayPalIPN = apps.get_model("ipn", "PayPalIPN") for ipn in PayPalIPN.objects.all(): # Need to recreate PayPalIPN.posted_data_dict posted_data_dict = None if ipn.query: from django.http import QueryDict roughdecode = dict(item.split('=', 1) for item in ipn.query.split('&')) encoding = roughdecode.get('charset', None) if encoding is not None: query = ipn.query.encode('ascii') data = QueryDict(query, encoding=encoding) posted_data_dict = data.dict() if posted_data_dict is None: continue for field in ['time_created', 'payment_date', 'next_payment_date', 'subscr_date', 'subscr_effective', 'retry_at', 'case_creation_date', 'auction_closing_date']: if field in posted_data_dict: raw = posted_data_dict[field] naive = parse_date(raw) if naive is not None: aware = timezone.make_aware(naive, pytz.timezone('US/Pacific')) setattr(ipn, field, aware) ipn.save() class Migration(migrations.Migration): dependencies = [ ('ipn', '0003_auto_20141117_1647'), ] operations = [ migrations.RunPython(fix_ipn_dates, lambda apps, schema_editor: None) # allowing reverse migration is harmless) ]
- Fixed various deprecation warnings when running under Django 1.8
- Added ‘commit’ kwarg to
PayPalFailure.nvpattribute to get full info
- Switched to using
requestslibrary for HTTP calls.
Introduced new, less confusing signals, and deprecated the old ones. This is a bit of an API overhaul, but the migration path is clear, don’t worry!
Previously, there were IPN signals like
payment_was_successfulwhich fired even if the
payment_statuson the IPN was
'Failed', and there were other signals like
payment_was_refundedto cover other specific statuses, but not all of them. There were also bugs that meant that some signals would never fire.
To sort out all these issues, and to future proof the design, the signals have been reduced to:
The ‘invalid’ signals are sent when the transaction was flagged - because of a failed check with PayPal, for example, or a duplicate transaction ID. You should never act on these, but might want to be notified of a problem.
The ‘valid’ signals need to be handled. However, you will need to check the payment_status and other attributes to know what to do.
The old signals still exist and are used, but are deprecated. They will be removed in version 1.0.
Please see Using PayPal Standard IPN.
This used signals even though they weren’t really appropriate.
- If you are using PayPalWPP directly, the returned PayPalNVP objects from all method should just be used. Remember that you need to handle PayPalFailure exceptions from all direct calls.
- If you are using the PayPalPro wrapper, you should pass a callable nvp_handler keyword argument.
Please see Using PayPal Payments Pro (WPP).
You must explicitly set
Falsein your settings, depending on whether you want production or sandbox PayPal. (The default is
Truei.e. sandbox mode).
sandbox()method on any forms is deprecated. You should use
PAYPAL_TESTin your settings instead.
Fixed support for custom User model in South migrations
- are using a custom AUTH_USER_MODEL
- are using the ‘pro’ app
- installed version 0.1.4 and ran the migrations,
you will need to reverse the migrations in the ‘pro’ app that were applied when you ran ”./manage.py migrate”.
- New docs!
- Python 3 support.
- Django 1.7 support.
- Support for custom User model via AUTH_USER_MODEL. If you change AUTH_USER_MODEL you will still need to write your own migrations.
- Support for all possible ‘initial’ options that could be wanted in PayPalStandardForm
- Support for PayPalPro CreateBillingAgreement method
- Support for PayPalPro DoReferenceTransaction method
- Upgraded to PayPal Pro API version 116.0
- This deprecates the “amt” parameter for SetExpressCheckout and DoExpressCheckoutPayment. paymentrequest_0_amt should be used instead. Use of amt will raise a DeprecationWarning for now.
- Various bug fixes, refactorings and small features.
- Removed PDT signals (which were never fired)
- Missing payment types added
- Additional signals:
- Django 1.6 compatibility
- Various bug fixes, including:
- Fixes for non-ASCII characters