Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Transaction Type and ID mandatory | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Transaction Type and ID mandatory

Transaction Type and ID mandatory

Posted: July 11, 2013 at 10:44 am

Viewing 4 reply threads


tkapena

July 11, 2013 at 10:44 am

Hi,

How can I make these 2 fields not required when updating payment?

The feature’Enter New Payment Amount’ and then status updates automatically is somehow useful but why not leave option of completing transaction the old way also available. Maybe I have not analysed lots of scenarios for this new procedure but much more time is being spent on inputting required info compared to previously were one would just set ‘Completed’.

I have brought this considering on-premise check in where you have people lining up and registration team have to deal with them double fast.

Lastly, I’m not weather to blame my users but a lot of them always don’t complete registration resulting in empty ‘Transaction Type’, thus part of the reason I asked the question of making the fields not mandatory.

Any insight much appreciated


Sidney Harrell

  • Support Staff

July 11, 2013 at 12:07 pm

In the file includes/admin-reports/enter_attendee_payments.php, comment out lines 72-82 to remove the transaction type and id requirements. Comment out lines 91-99 to remove the automatic payment status updating.


tkapena

July 15, 2013 at 3:25 am

Thanks Sidney,

I’m on 3.1.33, so I commented out 70-82 and 89-95 specifically and both areas works well. Really helpful in my current state of operations.


Josh

July 15, 2013 at 10:03 am

I’ve added a ticket so that in future versions the code that makes the transaction type and ID mandatory can be filtered or unhooked via a function so it will not be necessary to directly edit core files. It will likely not make it into the next two shipping versions, so you’ll need to re-edit the customizations after updating.


tkapena

July 16, 2013 at 2:06 am

Thanks Josh, sounds good.

Viewing 4 reply threads

The support post ‘Transaction Type and ID mandatory’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server