do not use birthday property in Credential Request or Credential Update, because its storage is start_date and start_date has different meaning in these portal types. add assertions to check if birthday is set by credential request, and not updated unexpectedly by credential update.

clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and through the activities and added one test to cover this method

Fix unit test

Revert "clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method"

This reverts commit 03e358bc.

One test was failing

clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method

remove paramater that is not supported on IPaymentService and refactor code to be possible pass a list of parameters to page template. With this will be possible create one form more ergonomic to post to paypal

Forgot to bump egg version.

This is ERP5SecurePayment service which aims to provide paypal integration following ERP5SecurePayment interface.

Revert 97d2dbbb (we do not need to generate all entries per feed request only the most recent once as client code is expected to keep a "local" copy instead).

Revert 17045076 (we do not need to generate all entries per feed request only the most recent once as client code is expected to keep a "local" copy instead).

use the interpreter's import lock instead of threading.RLock in ERP5Type.dynamic to avoid possible dead lock.

Make sure the failure in testLegacyDeliveryBuilderToSupportMultipleLines.TestNestedLine.test_04_MergingMultipleSaleOrders happens always.

It was random because of the order of executed activities.

Make sure Web Message events are properly reindexed after creation, before the fetch_incoming_web_message_list alarm is run

thinko: inverted logic

Don't fail if a previous --save test was interrupted before cleanup.

Delete in beforeTearDown() the person that was added on afterSetUp().

In ERP5, objects that do not acquire local roles (according to their portal type configuration) do not need to be reindexed with their containers.
So do not reindex recursively if portal_types of contained objects don't need it.

Security reindexing can be customized with a type-based method.

Fix test that wrongly relied on unrestricted access for updating object roles.

Don't fix the default_encoding at import time as it can be overriden later (ex. by a later import of zope configuration).

Don't assume objects to be str if they're not unicode