|
David Holland
|
January 26, 2014 at 2:16 pm
The Infusionsoft add-on needs to use the service addWithDupCheck and not the add service it currently uses. If not then the whole point of Infusionsoft segmentation is undermined as duplicate records are created and will not have the correct tags in existence.
Creating new products every time a ticket is sold is ridiculous. If you sell 100’s of tickets you get 100’s products. If you have 100’s of events you get 1000’s of products. This undermines the RoI tracking and reporting.
Not treating sales tax as a separate line item on an invoice is illegal in the UK. So both Event Espresso and Infusionsoft invoices are illegal to send.
So close…but not close enough to be able to use this. I have bought the Infusionsoft add-on, but it needs to be fixed to be usable. Can you please give some visibility to if these issue will be fixed soon or when.
These little tweaks will make this awesome plug-in world class.
|
|
Sidney Harrell
|
January 27, 2014 at 9:27 am
The duplicate products problem should have been fixed in version 1.2 of the infusionsoft add-on. Do you have html tags in your event name or price description?
I’ll raise a ticket to have the tax issue looked at. In the meantime, this invoice template may help: https://gist.github.com/Apina/5857667
|
|
David Holland
|
January 27, 2014 at 12:21 pm
I am on Infusionsoft Integration v1.2 and it is definitely creating duplicate products. There are no html tags in the event name or price description.
It also creates to duplicate contacts as the wrong service is being use in the API. Can you raise a ticket to get that fixed too please?
Want do I do with the invoice template?
|
|
Sidney Harrell
|
January 27, 2014 at 5:14 pm
The contact is already being added with the duplicate check, (index.php line 121).
The only reason the event is not added with a call to add with dup check is we are already checking for a duplicate on our end. We do a call to query for an existing product, (line 180) so that we can have the existing product’s id to use when we add the order item that links the contact with the product. Are you able to reproduce the duplication on a test setup, or is this only on a live server? I would like to put in a debugging line at 187, to query by the product id that we get from line 183, so we can compare what infusionsoft is storing for the event product data to what we are sending it (lines 172-177). If it’s a live server, then we can wrap the debugging output in html comment tags, so the users would not see it.
|
|
Seth Shoultes
|
January 28, 2014 at 11:56 am
Regarding the display of taxes in the invoice. Maybe this will help?
https://eventespresso.com/wiki/using-a-custom-invoice-template-to-support-vat/
|
|
David Holland
|
January 28, 2014 at 1:57 pm
Hooked this up to a sandbox with a live merchant account. There are no duplicates being created for contacts or products, which is great.
In the order record this is showing the transaction twice. Once labelled credit card and the other labelled Manual. So the ledger is wrong.
http://goo.gl/OW8Ist
|
|
Sidney Harrell
|
January 28, 2014 at 2:31 pm
Ouch! Sorry, that may be my fault. If you are using the infusionsoft payment gateway, comment out line 232 in plugins/espresso-infusionsoft/index.php:
add_filter('filter_hook_espresso_update_attendee_payment_data_in_db', 'espresso_save_infusionsoft_manual_payment', 100, 1);
I had put that in so that if you used one of the EE payment gateways, it would update the infusionsoft record. We’ll try to get that fixed before we release another update to the infusionsoft add-on.
|
