andjules70

Thanks for answering, Tobias, I appreciate it.

Thank you! That worked.

+1. Critical feature. Any help appreciated.
https://github.com/katzwebservices/Gravity-Forms-Directory/issues/34

• This reply was modified 6 years, 6 months ago by andjules70.

We’re having the reverse problem: after recently upgrading the plugin, smartapproval has unexpectedly kicked in (so each form entry is defaulting to not-approved and now requires manual approval), even though our form does not have a field which could/should be detected as being an ‘approval’ field.

I don’t the developers will answer, but the way the elavon tab works for amount (and all the other optional fields) is you enter the fieldname (not it’s label) from your form tab for the field that will contain the amount. In other words, you’re supposed to design the first step of the form (using the form tab) and it should, at the very least, include an ‘amount’ field.

For example: your ‘FORM’ might be configured with two fields:

<p>Payment Amount<span class="required">*</span>
[text* myamount]</p>
<p>City <span class="required">*</span>
[text* mycity]</p>

So on the Elavon tab, you’d enter ‘myamount’ for amount (the field that will be passing the transaction amount) and optionally, you could enter ‘mycity’ for City (the field that will pass the value for City).