1.3.0
版本发布时间: 2017-01-23 01:57:01
schmittjoh/JMSPaymentCoreBundle最新发布版本:1.4.1(2019-02-21 02:44:35)
Changed
-
JMS\Payment\CoreBundle\Model\ExtendedDataInterface
has changed. If any of your classes implement this interface, you need to update them accordingly:- Added missing
mayBePersisted
method - Added missing
$persist
parameter toset
method
- Added missing
-
JMS\Payment\CoreBundle\EntityExtendedDataType::convertToDatabaseValue
now throws an exception when attempting to convert an object which does not implementJMS\Payment\CoreBundle\Model\ExtendedDataInterface
. - Encryption is now optional and disabled by default, unless the
secret
orencryption.secret
configuration options are set. -
defuse_php_encryption
is now the default encryption provider, unless when using thesecret
configuration option, in which case the default is set tomcrypt
. - The EntityManager is no longer closed when an Exception is thrown (#145)
Deprecated
- The service
payment.encryption_service
has been deprecated and is now an alias topayment.encryption.mcrypt
. Parameters specified forpayment.encryption_service
are automatically set forpayment.encryption.mcrypt
so no changes are required in service configuration untilpayment.encryption_service
is removed in 2.0. - The
secret
configuration option has been deprecated in favor ofencryption.secret
and will be removed in 2.0. Please note that if you start usingencryption.secret
you also need to setencryption.provider
tomcrypt
since mcrypt is not the default when using theencryption.*
options. -
JMS\Payment\CoreBundle\Cryptography\MCryptEncryptionService
has been deprecated and will be removed in 2.0 (mcrypt
has been deprecated in PHP 7.1 and is removed in PHP 7.2). Refer to http://jmspaymentcorebundle.readthedocs.io/en/stable/guides/mcrypt.html for instructions on how to migrate away frommcrypt
.
Added
- Added
method_options
andchoice_options
to form. See the documentation for more information. - Added a guides section to the documentation
- Added support for custom encryption providers.
- Added support for data encryption with defuse/php-encryption.
- Added console command to generate an encryption key for use with
defuse_php_encryption
. - Added ability to configure which encryption provider should be used. Current available options are
mcrypt
(not recommended since it will be removed in PHP 7.2) anddefuse_php_encryption
.
Removed
- Removed support for PHP 5.3. If you're still using PHP 5.3, please consider upgrading since it reached End Of Life in August 2014. Otherwise, use
1.2.*
.