bfl
Forum Replies Created
-
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] PHP ErrorHey. The plugin should still work properly before the Create button is pressed. This is because every load of the Add new order page actually creates a new order. This means that something else is going wrong here. If you’re interested in fixing this bug, you can provide a WooCommerce system report and I’ll try to reproduce the issue. None of my test sites have this problem, so it must be specific to certain environments.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] PHP ErrorHey @clarityconnect. The stack trace is cut off. Could you please provide the rest? Thanks.
Hey @keithmorr and @khernandez. Is there any PHP error being logged?
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] BraintreeHey @jpaytoncfd. I got a couple requests for new gateways recently, and I’m still working through them. If you don’t mind waiting a few weeks, I can reply to this thread when I’m available. You can also reach me at bfl.wordpress.org@gmail.com. Thanks.
Hey @eliotmross. You can turn off the Include Billing Details option in the plugin settings. This might prevent Authorize.Net from being able to try matching addresses. You can also try turning off that AVS filter in your Authorize.Net Merchant Interface (Fraud Detection Suite > Enhanced AVS Handling Filter). Let me know if that helps.
Does your regular gateway plugin send billing details to Authorize.Net? If it doesn’t, that could explain why it doesn’t trigger that filter.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Add a payment gateway?Hey. This may be something I can do. I’ve sent you an email.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Customisation request – eWay@lukekenny I’ve confirmed that this is something I can do. You can contact me at bfl.wordpress.org@gmail.com.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Add a payment gateway?Hey @headsaflame. I’m looking into Elavon and I’ll follow up soon.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] All orders declining as of ThursdayCan you create a test order with your own card and try processing a small payment to see if the issue is ongoing?
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] All orders declining as of ThursdayIs this issue currently happening with all orders? Can you please check your Authorize.Net Merchant Interface to see if those failed transactions have any additional information about their failure?
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] Customisation request – eWayHey @lukekenny. It is possible. I’m looking into this and I’ll get back to you soon.
Hey. Any update on this issue? You can also try checking WooCommerce > Status > Logs to see if there’s an option for a log file with a name starting with “fatal-errors”. If there is, you can use that to see what error is being triggered when you process a payment. However, this log file will only show you fatal errors. If the error causing the issue is not a fatal error, then you will not see it there.
Forum: Plugins
In reply to: [Backend Payments for WooCommerce] All orders declining as of ThursdayCan you please copy and paste the entire error message along with any details that show up when you click Details ▼ (on the right side of the error message, if applicable)? The error message will indicate the reason for the declination. You can also look up the declined transactions in the Authorize.Net Merchant Interface.
Hey. I just released a new version which adds additional details to Authorize.Net error messages.
Thank you. Would it be possible to get the PHP error message that is being logged when you make a payment? If you’re not sure how to do this, you can use this plugin to monitor the error log. In order for that plugin to work, you will need to add a few lines to wp-config.php:
Above this line:
/* That's all, stop editing! Happy blogging. */Write:
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);