furioussnail

That's it. Thank you.

This is correct. I have been migrated to their new platform. I didn't use the sandbox. Those are results using a live account. We have already been working with 2checkout for a while now but the plugin has never worked fully. Thank you for your help.

Hello. With Support Manager enabled, is it possible to setup a per agent signature which is added automatically when an agent replies? If yes, then how do I do that? Thank you.

@Tyson could you please have a look and confirm? Thank you.

Hello. Using latest Blesta version, 4.5.0. The ticketing system seems to be working properly only with {ticket_hash_code} in the subject. The problem with it compared to the {ticket.code} tag is that it breaks the conversation style in Gmail and similar email services. Relying on {ticket.code} should be enough. Or am I missing something? At least that's how majority of help desk software out there is working. Using {ticket.code} instead of {ticket_hash_code} in the subject line constantly generates new tickets. Thank you.

The fix is simple. At least for my use case. Removing 'reply_to' => $ticket->department_email from plugins/support_manager/models/support_manager_tickets.php I think the plugin should honor the email setup in the templates. After all there is this option when configuring a department: "Override the from address set in email templates with the email address set for this department". I hope this will be included in the next update.

Hello. Support Manager is setting a reply-to header. At least in my case that brings issues. The thing is I want my customers to send support requests to support@example.com. But since we are using G Suite with piping I had to setup a forward to support@support.example.com. As a result a customer sends an email to support@example.com and it gets redirected to support@support.example.com. Now, in Blesta the email address for the support department is set to support@support.example.com but the templates related to the module have the "From" email address set to support@example.com. The problem is Support Manager sends a "reply-to: support@support.example.com" to all ticket related messages. This shouldn't happen since support@support.example.com is just an internal address. Could you please fix this behaviour? This happens on Blesta 4.5.0. Thank you.

Another thing, 2checkout sandbox seems to be using the old interface. Not sure how different is that compared to the latest thing they have for live transactions. Thank you for your help guys.

Just noticed that for one payment through 2checkout blesta records 7 fields. All have errors. The very first field is something like this: /callback/gw/1/_2checkout/?middle_initial=&sid=2*********&key=8*********&state=CU&email=e*********.com&submit.y=28&order_number=2*********&cart_id=1-*********&currency_code=U*&lang=en&invoices=Y*********&invoice_id=2*********&total=5.00&credit_card_processed=Y&zip=2*&cart_weight=0&fixed=Y&last_name=C*********&street_address=M*********&city=C*********&cart_order_id=1-*********&merchant_order_id=&country=M*&ip_country=M*********&demo=N&submit.x=196&client_id=1&pay_method=CC&cart_tangible=N&phone=3*********+&x_receipt_link_url=https%3A%2F%2Fp*********.com%2Fcallback%2Fgw%2F1%2F_2checkout%2F&street_address2=&first_name=Emil&card_holder_name=E*********&PTCOID=a*********a:3:{s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;} then a couple similar to this one: a:59:{s:7:"sale_id";s:12:"2**********";s:16:"sale_date_placed";s:19:"2019-02-26 04:31:16";s:9:"recurring";s:1:"0";s:12:"payment_type";s:11:"credit card";s:13:"list_currency";s:3:"U*";s:12:"fraud_status";s:4:"pass";s:9:"vendor_id";s:9:"2**********";s:15:"vendor_order_id";s:0:"";s:10:"invoice_id";s:12:"2**********";s:14:"invoice_status";s:9:"deposited";s:19:"invoice_list_amount";s:5:"*.00";s:18:"invoice_usd_amount";s:5:"*.00";s:19:"invoice_cust_amount";s:5:"*.00";s:10:"item_count";s:1:"1";s:8:"auth_exp";s:10:"2019-03-05";s:19:"customer_first_name";s:6:"T**********";s:18:"customer_last_name";s:7:"M**********";s:13:"customer_name";s:14:"T********** M**********";s:14:"customer_email";s:23:"t**********@**********.com";s:14:"customer_phone";s:11:"1**********";s:11:"customer_ip";s:14:"184.*.*.*";s:19:"customer_ip_country";s:24:"U**********";s:13:"cust_currency";s:3:"U*";s:9:"bill_city";s:11:"P**********";s:12:"bill_country";s:3:"U*";s:16:"bill_postal_code";s:5:"9**********";s:10:"bill_state";s:2:"C*";s:19:"bill_street_address";s:21:"4**********";s:20:"bill_street_address2";s:11:"Suite #D503";s:11:"ship_status";s:0:"";s:20:"ship_tracking_number";s:0:"";s:9:"ship_name";s:14:"M**********";s:19:"ship_street_address";s:21:"4**********";s:20:"ship_street_address2";s:11:"S**********";s:9:"ship_city";s:11:"P**********";s:10:"ship_state";s:2:"C*";s:16:"ship_postal_code";s:5:"9**********";s:12:"ship_country";s:3:"U*";s:10:"message_id";s:5:"1**********";s:12:"message_type";s:22:"INVOICE_STATUS_CHANGED";s:19:"message_description";s:22:"Invoice status changed";s:9:"timestamp";s:19:"2019-02-26 11:33:33";s:11:"item_name_1";s:29:"Cart purchase: 2**********";s:9:"item_id_1";s:13:"23-**********";s:18:"item_list_amount_1";s:5:"*.00";s:17:"item_usd_amount_1";s:5:"*.00";s:18:"item_cust_amount_1";s:5:"*.00";s:11:"item_type_1";s:4:"bill";s:15:"item_duration_1";s:7:"Forever";s:17:"item_recurrence_1";s:0:"";s:22:"item_rec_list_amount_1";s:0:"";s:17:"item_rec_status_1";s:4:"live";s:20:"item_rec_date_next_1";s:0:"";s:25:"item_rec_install_billed_1";s:0:"";s:8:"md5_hash";s:32:"D********************";s:9:"key_count";s:2:"55";s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;} and last two of these: /callback/gw/1/_2checkout/ a:3:{s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;}

In 2checkout I setup https://p*****.com/callback/gw/1/_2checkout/ for INS and exactly the same as a return link. The return is done through "Header redirect".

One warning in general-warning log file: [2019-02-27 22:45:30] general.WARNING: E_WARNING: Invalid argument supplied for foreach() {"code":2,"message":"Invalid argument supplied for foreach()","file":"/srv/p*********.com/http/app/controllers/client_pay.php","line":915}

On last test I got something a bit different: /callback/gw/1/_2checkout/?middle_initial=&sid=2*********&key=8*********&state=CU&email=e*********.com&submit.y=28&order_number=2*********&cart_id=1-*********&currency_code=U*&lang=en&invoices=Y*********&invoice_id=2*********&total=5.00&credit_card_processed=Y&zip=2*&cart_weight=0&fixed=Y&last_name=C*********&street_address=M*********&city=C*********&cart_order_id=1-*********&merchant_order_id=&country=M*&ip_country=M*********&demo=N&submit.x=196&client_id=1&pay_method=CC&cart_tangible=N&phone=3*********+&x_receipt_link_url=https%3A%2F%2Fp*********.com%2Fcallback%2Fgw%2F1%2F_2checkout%2F&street_address2=&first_name=Emil&card_holder_name=E*********&PTCOID=a********* a:3:{s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;}

I apologize. I noticed just a bit later the type of transaction. All transactions record the same behaviour: a:59:{s:7:"sale_id";s:12:"2**********";s:16:"sale_date_placed";s:19:"2019-02-26 04:31:16";s:9:"recurring";s:1:"0";s:12:"payment_type";s:11:"credit card";s:13:"list_currency";s:3:"U*";s:12:"fraud_status";s:4:"pass";s:9:"vendor_id";s:9:"2**********";s:15:"vendor_order_id";s:0:"";s:10:"invoice_id";s:12:"2**********";s:14:"invoice_status";s:9:"deposited";s:19:"invoice_list_amount";s:5:"*.00";s:18:"invoice_usd_amount";s:5:"*.00";s:19:"invoice_cust_amount";s:5:"*.00";s:10:"item_count";s:1:"1";s:8:"auth_exp";s:10:"2019-03-05";s:19:"customer_first_name";s:6:"T**********";s:18:"customer_last_name";s:7:"M**********";s:13:"customer_name";s:14:"T********** M**********";s:14:"customer_email";s:23:"t**********@**********.com";s:14:"customer_phone";s:11:"1**********";s:11:"customer_ip";s:14:"184.*.*.*";s:19:"customer_ip_country";s:24:"U**********";s:13:"cust_currency";s:3:"U*";s:9:"bill_city";s:11:"P**********";s:12:"bill_country";s:3:"U*";s:16:"bill_postal_code";s:5:"9**********";s:10:"bill_state";s:2:"C*";s:19:"bill_street_address";s:21:"4**********";s:20:"bill_street_address2";s:11:"Suite #D503";s:11:"ship_status";s:0:"";s:20:"ship_tracking_number";s:0:"";s:9:"ship_name";s:14:"M**********";s:19:"ship_street_address";s:21:"4**********";s:20:"ship_street_address2";s:11:"S**********";s:9:"ship_city";s:11:"P**********";s:10:"ship_state";s:2:"C*";s:16:"ship_postal_code";s:5:"9**********";s:12:"ship_country";s:3:"U*";s:10:"message_id";s:5:"1**********";s:12:"message_type";s:22:"INVOICE_STATUS_CHANGED";s:19:"message_description";s:22:"Invoice status changed";s:9:"timestamp";s:19:"2019-02-26 11:33:33";s:11:"item_name_1";s:29:"Cart purchase: 2**********";s:9:"item_id_1";s:13:"23-**********";s:18:"item_list_amount_1";s:5:"*.00";s:17:"item_usd_amount_1";s:5:"*.00";s:18:"item_cust_amount_1";s:5:"*.00";s:11:"item_type_1";s:4:"bill";s:15:"item_duration_1";s:7:"Forever";s:17:"item_recurrence_1";s:0:"";s:22:"item_rec_list_amount_1";s:0:"";s:17:"item_rec_status_1";s:4:"live";s:20:"item_rec_date_next_1";s:0:"";s:25:"item_rec_install_billed_1";s:0:"";s:8:"md5_hash";s:32:"D********************";s:9:"key_count";s:2:"55";s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;}

For PayPal I see two fields in the log, Output and Input. That's not the case for 2checkout. Only Output is displayed. Thank you.

Didn't want to post that since I see no errors there and most of the data is private. Anyway, here it goes: /callback/gw/1/_2checkout/ a:53:{s:7:"sale_id";s:12:"2**********";s:16:"sale_date_placed";s:19:"2019-02-26 00:37:42";s:9:"recurring";s:1:"0";s:12:"payment_type";s:11:"credit card";s:13:"list_currency";s:3:"USD";s:9:"vendor_id";s:9:"2**********";s:15:"vendor_order_id";s:0:"";s:10:"invoice_id";s:12:"2**********";s:10:"item_count";s:1:"1";s:19:"customer_first_name";s:4:"E**********";s:18:"customer_last_name";s:11:"C**********";s:13:"customer_name";s:16:"E********** C**********";s:14:"customer_email";s:15:"e**********@**********.com";s:14:"customer_phone";s:11:"3**********";s:11:"customer_ip";s:11:"89.*.*.*";s:19:"customer_ip_country";s:20:"M**********";s:13:"cust_currency";s:3:"USD";s:9:"bill_city";s:8:"C**********";s:12:"bill_country";s:3:"M**";s:16:"bill_postal_code";s:4:"2***";s:10:"bill_state";s:2:"C*";s:19:"bill_street_address";s:43:"M**********";s:20:"bill_street_address2";s:0:"";s:11:"ship_status";s:0:"";s:20:"ship_tracking_number";s:0:"";s:9:"ship_name";s:16:"C**********";s:19:"ship_street_address";s:43:"M**********";s:20:"ship_street_address2";s:0:"";s:9:"ship_city";s:8:"C**********";s:10:"ship_state";s:2:"C*";s:16:"ship_postal_code";s:4:"2***";s:12:"ship_country";s:3:"M**";s:10:"message_id";s:5:"1****";s:12:"message_type";s:13:"REFUND_ISSUED";s:19:"message_description";s:13:"Refund issued";s:9:"timestamp";s:19:"2019-02-26 15:12:52";s:11:"item_name_1";s:28:"Cart purchase: 1-**********";s:9:"item_id_1";s:12:"1-**********";s:18:"item_list_amount_1";s:4:"5.00";s:17:"item_usd_amount_1";s:4:"*.00";s:18:"item_cust_amount_1";s:4:"*.00";s:11:"item_type_1";s:6:"refund";s:15:"item_duration_1";s:7:"Forever";s:17:"item_recurrence_1";s:0:"";s:22:"item_rec_list_amount_1";s:0:"";s:17:"item_rec_status_1";s:4:"live";s:20:"item_rec_date_next_1";s:0:"";s:25:"item_rec_install_billed_1";s:0:"";s:8:"md5_hash";s:32:"E**********************";s:9:"key_count";s:2:"49";s:4:"demo";N;s:12:"order_number";N;s:5:"total";N;} Maybe I am missing something. Thank you.

Yes, Blesta does receive an INS transaction and marks it with "Error". "Tools" -> "Logs" -> "Gateway" is where I checked. Thank you.

The funny part is 2checkout reports the INS sessions as successful but Blesta reports them with Error.

Could you please have a look at the 2checkout plugin? I am a bit desperate. This is a long time issue. Also, maybe you can enable recurring billing. I see that the guys at the WHMCS did it. Thank you.

I did add the correct link, at least it's similar tot he one you provided, into the "Enable global URL" field at 2checkout. Also I enabled the redirect. To the same URL. This still isn't working. I am starting to get a bit mad at the Blesta team. This isn't the first time I asked for help without any results. 2checkout probably isn't the best solution but it is the only one available in my country. Thank you everyione for your help.

Thank you for your input and sorry for late reply. I am not sure what's the cause for this issue. I never had 2checkout working properly. Till now I processed all the order going through 2checkout manually. Since 2checkout was aquired by Avangate it looks like they did extensive updates and modifications to the platform and I am not sure even where to start. Blesta documentation related to 2checkout is very scarce. I was looking for some payment alternatives but at this time I have nothing, mostly due to the country where I live. Could you please provide some instructions on how to setup it? Does your setup support recurring payments? Thank you.

Probably I didn't explain the issue properly. In my opinion a bit to many actions are being logged to the database. Once the customer base grows this impacts performance. Maybe allowing the admins to choose which actions are being logged would be a viable solution. Thank you.

Yes, that helped. My question regarding the amount of logs saved to the database still stands. Aren't they a bit too much? Thank you.

I added 2>&1. I will wait to see if that helps. However, the question about the amount of recorded logs is still standing. That output to the database is a bit much in my view. Thank you.

At some point I started receiving all the Blesta logs by email. I am using the latest version. Any idea where the problem might be? Also, isn't Blesta logging a bit too much? For one day I have hundreds of log pages (Tools -> Logs -> Cron). Thank you.

Not sure about you guys but we were updated to their new 2Checkout V2.0 platform. The new version acts as a billing panel in itself. The update makes it really difficult to use it as a simple payment gateway. Thank you for your suggestions.