CiviCRM Community Forums (archive)

Hi All,

Its my pleasure to be part of civiCRM.

Recently we have developed a payment procedure in civiCRM 4.1 with joomla 1.7. Do we know how do we submit it to civiCRM so that they may release it in further releases. Previously we have submitted it to civiCRM. Now we have changed the way the system handling the billing mode.

Please guide us how to submit it to civiCRM as early as possible.

Thanks in advance.

Regards,
Adiyya Tadikamalla

Thanks lobo for quick response. Sorry for the late reply. Iam away from my system for few days.


Thanks,
Adiyya T

Hello, Addiya,

Your problem description makes sense (although it's a new situation we haven't encountered before). The "civicrm_payment_processor_type" table requires that each "name" be unique, and it does appear that the "name" is already used by some other code in core. The simplest solution would be to use different name for the extension variant -- eg "ClickAndPledgeExt" or "ClickAndPledge2". (I'd give you more details on renaming -- but that depends on how exactly the extension is written -- eg in info.xml, does it declare the extension type as "payment" or "module"?)

The simple approach comes with one drawback -- administrators who have previously configured "ClickAndPledge" payment processors will need to revise the configuration. That's probably a reasonable thing to do (since they have access to two different implementations and may want to try out each). However, if you really want to do this automatically, then you might use something like this pseudocode:

function clickandpledge_civicrm_enable() {
    // If core defines older ClickAndPledge, then migrate data and disable it
    sql("UPDATE payment_processor
      SET payment_processor_type = ClickAndPledgeExt
      WHERE payment_processor_type = ClickAndPledge")
    sql("UPDATE payment_processor_type
      SET is_active = 0
      WHERE name = ClickAndPledge")
 }

 function clickandpledge_civicrm_disable() {
    // If core defines older ClickAndPledge, then restore it
    sql("UPDATE payment_processor_type
      SET is_active = 1
      WHERE name = ClickAndPledge")
    sql("UPDATE payment_processor
      SET payment_processor_type = ClickAndPledge
      WHERE payment_processor_type = ClickAndPledgeExt")
 }

Implementing the above may take a bit of effort because that hasn't been done before, it requires testing for corner cases, and some of the documentation for implementing payment processors needs revision for 4.2. Also, the specific codes depend on the declared extension-type ("payment" or "module").

Final note: In two spots, I've mentioned that extensions can be of type "payment" or "module". For 4.2+, "module" is the better approach, but there are some gaps in documentation regarding payment-processing. But fortunately there is an example:

https://github.com/drastik/civicrm_stripe/tree/master/extension-4.2/com.drastikbydesign.stripe

hey kamran:

can u please file an issue for this. we'll take care of it in 4.2.1

lobo