CiviCRM Community Forums (archive)

I suspect that processor_id field is an old one that will disappear, sounds like a dangerous thing to assume will continue.

I think that inherently what you are doing is creating a payment processor that does nothing except give a nod to something happening outside of civicrm. So creating a "dummy" payment processor isn't so much a hack as a good representation of what this module is doing. For example, if later on someone looks at a particular contribution, they may want to know how to find the money this transaction refers to. By linking that transaction to this 'dummy' processor [which can be customized per install with details about how the transactions are actually getting done outside of civicrm], it makes the whole thing a bit more accountable.

In general, this money thing is pretty confusing, and it's good to distinguish clearly between an actual transaction and the various kinds of records of a transaction and how they may or may not be related ..

Hi

I've just tried to install this extension via civi manage extensions and I get the error screen attached  and the installation fails.  I'm running 4.3.5

Any suggestions?

Adrian
Cambridge Rugby

The current version, 1.3, appears to remain incompatible with offering recurring payments via, e.g., PayPal on a CiviCRM online donation page.  (This is the only version I've installed, so the problem isn't an update issue.)

Andy -  FYI - I'm looking at using the recurring processor in 4.4 in the following flow
- backoffice person uses front-office form to set up recurring - selects a payment type which maps to offline recurring
- civixero pushes contact to xero
- a matching rule is set up in xero for that person's bank payments as they come in
- civixero pulls the payment & creates the contribution
- in 4.4 it's now possible to search on next scheduled payment date so we will use that to track missing incomings

I've had a problem with this extension in 4.4.  The problem was the contribution configuration page wouldn't allow a payment processor to be selected, and also two blocks of help  text was down-level.  When this extension was removed the problem went away.  Is this extension compatible with 4.4, or did I jump the gun?

Ok, well the issues with payment processor selection should now be fixed - we rolled out a new version of it the other week. Sorry for the delay in doing that, but Circle reckons this kind of stuff is never a priority unfortunately - so it basically ends up being a case of me doing it in my spare time if I want it done, then the company takes credit for it.

The extension is not currently 4.4 compatible, it should state that on the extension's release page, plus in the info.xml file that comes with the extension.

I am working with another member of the community at the moment to make this 4.4 compatible though, so we'll have a look at some of that stuff you've pointed out lobo, thanks for that, and hopefully get a new version out in the next week or so.

But this wasn't my code originally, we just ported it to an extension so it would run on Drupal 7 - it does use a lot of template customizations, but I've discovered a lot of them aren't necessary and have been causing problems - so we'll try and get all of those removed, and see if we can handle the remaining ones in a more upgrade-proof way.

Hi

Do you have draft time scale for the new version

Many thanks

Jason tattersall


I really like you extension as it save me time.