|
Jason Paizes
|
December 26, 2014 at 11:33 pm
Hi team.. I have updated my license to EE4 as well as re-bought the Infusionsoft Plugin. One thing that is not intuitive is how to use Infusionsofts payment gateway rather than setting a payment gateway directly in EE. In V3 you could specify to use Infusionsoft but there does not seem to be such a setting in V4. All I can do is generate a manual invoice or use the few options under “Payment Methods”. Your documentation states that V4 can use Infusionsofts payment gateway so I was wondering if you could point me in the right direction to get this set up?
Thanks a million
Jason
|
|
Lorenzo Orlando Caum
|
December 29, 2014 at 9:45 am
Hi Jason,
The hosted payment gateways for Infusionsoft are available in Event Espresso 3 at this time. We will be introducing this in a future release of the Event Espresso 4 add-on.
There is a note about this here:
https://eventespresso.com/wiki/infusionsoft-integration/#gateway
Did you find some different information elsewhere? If so, could you share a link so we can get that clarified?
Thanks
—
Lorenzo
|
|
Jason Paizes
|
December 30, 2014 at 6:52 am
Hi Lorenzo.
There was confusion as you have mentioned in several places on your website that the plugin is integrated with the Infusionsoft Payment System… in hindsight this likely means that you update the payment status through integration but that it does not use the Infusionsoft Payment System like V3 did. I did not see the Wiki article before. The problem is that there are so few payment methods applicable to Australian users – the only one is likely to be used would be Payflow/PayPal Pro. I have developed a bridging plugin between EE and IS that allows for completely generic campaign handling (without having to create a new campaign for each event) which adds huge value, however, most people here use eWay and without a way to pay for the events (outside of manually or though PayPal) it makes it very difficult to sell the system as a full solution. I might have to stick with V3 for the time being.
Do you have an anticipated release date for the Payment Gateway integration?
I have purchased a developer licence of V4 as well as the Infusionsoft Integration. If there isn’t a workaround for this at the moment would it be possible for me to reverse this purchase as I am unlikely to be able to use it in the context of what I wanted to do (I still need to do some testing as there might be a workaround through the API).
Warm regards
Jason
|
|
Lorenzo Orlando Caum
|
December 30, 2014 at 10:07 am
Hi Jason, we do not have a release date for this feature. Would Event Espresso 3 work for your project needs?
—
Lorenzo
|
|
Jason Paizes
|
December 30, 2014 at 6:27 pm
Hi Lorenzo. V3 does work, and we have been using it for a few years. We hae also sold/implemented it with several clients. Since the release of V4 I’m finding it difficult to sell the integrated system when clients know that it’s not the latest version of the software – especially as a full integration takes a fair amount of time and can be fairly expensive. As my plugin (EventMx) does quite a lot in terms of dynamic campaign selection and population I’m reluctant to keep working on the old version and wanted to set it up in V4 and then market the solution (which is Event Espresso, Infusionsoft and EventMx as an integrated Event Management solution). I have the market and the resellers… it’s just this hiccough that is holding me up now.
Anyway… let me know your thoughts. In the meantime I am checking out options.
Cheers
Jason
|
|
Sidney Harrell
|
January 2, 2015 at 11:04 am
The work on converting the EE3 gateways to work with EE4 was put on hold pending a rewrite of the core-gateway interface. That work is in the upstream 4.6 branch, which is in Alpha. When we release 4.5 as the production-ready version, we’ll progress 4.6 to the pre-release channel. If you want to preview 4.6, then you can get github access here: https://eventespresso.com/developers/. Porting the EE3 version is not terribly difficult, but it is a little time consuming for the whole dev process when you include the testing cycles. We just couldn’t commit the resources for the 20+ EE3 gateways right away when they would all need to get ported again after the 4.6 rewrite.
|
