[TYPO3-paymentlib] compatibility break due to renaming of table fields

[Andrew Davis]

franz, did the compatibility check get implemented in 2.5.x ? i wonder 
if this isnt causing our problem?

andrew

Franz Holzinger wrote:
> Hello Tonni,
> 
>> Did you read the Changelog [1]? The fields are explained in there - as
>> well as in the README file.
> 
> Thanks. Feature-wish: Write an extension manual.
> 
>> The database layout almost directly reflected the iPayment gateway and
>> was changed to make it meaningful for more gateways - sorry for the
>> extra trouble. There will be at least one major change in the near
>> future with regards to replacing redirectURI with ok-/errorpage.
>>
>> Payment gateway/provider developers should always make sure to define
>> compatible versions of paymentlib in ext_emconf.
> 
> How? The extensions can be installed and used even without any
> paymentlib extension. The version of the paymentlib can only be
> suggested. In tt_products 2.6.0 there will be also a version check for
> the Payment Library, but inside of the code. If the installed version
> number of the Payment Library is too low, nothing will happen. Or maybe
> an error message should be displayed. Other installed extension might
> rely on a lower version of the Payment Library.
> 
> - Franz
>