|
laurian Horowitz
|
November 16, 2024 at 11:23 am
I just switched the authorize.net plugin from aim to accept. Now the payment section is narrow and requires horizontal scrolling. How do I adjust this to eliminate the horizontal scrolling while remaining adaptive to different device types?
Second, now there is a “pay button” and a “finalize registration” button (the latter had been the payment submit button only). Why are there 2 buttons and how do I eliminate one?
|
|
laurian Horowitz
|
November 16, 2024 at 11:23 am
I just changed the plugin from authorize aim to authorize accept and now the billing portion of checkout is not very wide. How do I change the view so that it is still adapting to devices and wide enough without scrolling horizontally?
|
|
Tony
|
November 19, 2024 at 10:12 am
Hi there,
I just changed the plugin from authorize aim to authorize accept and now the billing portion of checkout is not very wide. How do I change the view so that it is still adapting to devices and wide enough without scrolling horizontally?
I’ve been digging into this and have a fix for the accept add-on to prevent it from happening.
I’ll get it packaged up and pushed out for you shortly.
Second, now there is a “pay button” and a “finalize registration” button (the latter had been the payment submit button only). Why are there 2 buttons and how do I eliminate one?
AIM is an ONsite payment method in which your server handles the data and you click the ‘Finalize’ button as its part of the Single Page CheckOut process (SPCO for short) to send the payment request.
Accept is different, the payment fields are actually on Auth.net’s servers so you click the pay button there to initiate the payment. When you click on the pay button a request is sent back to your site which will triggers SPCO to ‘click’ the Finalize button for you.
In short, it’s due to the difference in how the integration methods work.
One thing you can is hide the finalize button but only when its been disabled using some CSS:
#spco-go-to-step-finalize_registration-submit.disabled {
display: none;
}
Add that to Appearance -> Customize -> Additional CSS
That finalize button would usually only be disabled if another payment method has loaded its own pay button and its waiting for the trigger I mentioned above, so this should be safe to do.
|
|
laurian Horowitz
|
November 20, 2024 at 11:57 am
Ok, thanks. Was able to hide the button. Looking forward to your solution on the width of the credit card info section.
|
|
Tony
|
November 21, 2024 at 6:34 am
The update was pushed live but if you can’t see it on your site just yet go to Event Espresso -> General Settings, make no changes and just hit save.
The update should then show in Dashboard -> Plugins, update to 1.0.5.p of the Auth.net Accept plugin and check the checkout page (you may need to hard refresh the page with Ctrl+F5).
|
