I have not dug into this but here is what happens
if (paymentConfig != null) {
paymentGatewayConfigId =
paymentConfig.getString("paymentGatewayConfigId");
configString = paymentConfig.getString("paymentPropertiesPath");
Debug.logInfo("using paymentConfig", module);
}
paymentGatewayConfigId !=null
configString = null
so
if (configString == null) {
configString = "payment.properties";
Debug.logInfo("using payment.properties", module);
}
sets the configString =="using payment.properties"
so when you get to getPaymentGatewayConfigValue()
it will try to read the db config instead of the payment properties.
Scott Gray sent the following on 6/17/2009 3:52 PM:
> Looks to me as though it will work fine so long as your
> ProductStorePaymentSetting for EXT_PAYPAL doesn't have a
> paymentGatewayConfigId set.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 18/06/2009, at 8:39 AM, BJ Freeman wrote:
>
>> for those that have not installed the entity paymentGateway and still
>> use the payment.properties
>>
>> the logic to select which one needs an new statement in the method
>> getPaymentGatewayConfigValue()
>> from
>> if (UtilValidate.isNotEmpty(paymentGatewayConfigId)) {
>>
>> to
>> if (UtilValidate.isNotEmpty(paymentGatewayConfigId)&&(resource
>> !="payment.properties")) {
>>
>> I am still preparing a patch this would be included in, that will not be
>> submitted for a few weeks.
>>
>> this is just a heads up if you having problems.
>>
>>
>>
>> --
>> BJ Freeman
>> http://www.businessesnetwork.com/automation
>> http://bjfreeman.elance.com
>> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
>>
>> Systems Integrator.
>>
>
--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.
