VirtueMart Forum

VirtueMart 2 + 3 + 4 => Plugins: Payment, Shipment and others => Topic started by: jdraper on July 06, 2020, 23:54:07 PM

Title: Payment plugin (Elavon) won't activate unless std payment method also selected
Post by: jdraper on July 06, 2020, 23:54:07 PM
We developed the Elavon payment method which was cloned from the Virtuemart authorize.net payment method.

(yes we stand on the shoulders of Valerie Isaksen and the VM team - kudos).

The Elavon plugin processes credit cards processed by Elavon merchant services company.

We have a report that the plug in will not display unless the standard payment method is also selected.

We have this running on multiple sites with no issues.

This site is running:

Joomla version 3.9.18
VirtueMart 3.8.2 10325
PHP version: 7.3.6

It may be an issue with the upgrade of VM from 3.6.10 to VM 3.8.2.

It is almost like the standard plugin runs some code that is a pre-requisite for the Elavon plugin.

Any ideas?

Thanks,

Jerry
Title: Re: Payment plugin (Elavon) won't activate unless std payment method also selected
Post by: jdraper on July 07, 2020, 00:14:33 AM
Validated that it is working on a site with VM 3.8.0 but they also have multiple payment methods configured.
Title: Re: Payment plugin (Elavon) won't activate unless std payment method also selected
Post by: GJC Web Design on July 07, 2020, 07:49:57 AM
This has been reported for the Authorize plugin before ..  ( although I thought it was fixed)  - might be on the forum here
I remember having to use a "hidden" std payment to get Auth to work on its own..
I assume u used the latest Auth plugin to base yours on?

It isn't extra code as I remember but something to do with detecting a valid plugin?
Title: Re: Payment plugin (Elavon) won't activate unless std payment method also selected
Post by: AH on July 07, 2020, 10:19:33 AM
I developed my own payment plugin for use with Elavon (via cardstream)

Cloning an existing plugin is useful - but clearly you have errors

I have no seen any errors - so it is clearly something you have done.

I worked with functions that were determined from a mixture of the standard plugin and the PayPal Standard plugin (which calls a third party HTML payment page and accepts a return url)