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
payment_date field in events_attendee table | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › payment_date field in events_attendee table

payment_date field in events_attendee table

Posted: December 24, 2012 at 12:54 am

Viewing 1 reply thread


hussain husain

December 24, 2012 at 12:54 am

you made weird mistakes there
first the type is varchar not date “which is not very bad”
second you use 2 type of dates at the same time

“Nov 21, 2012” and “21-11-2012”

so its nearly impossible to make me able to make payment report for accountant :


Josh

December 24, 2012 at 8:36 am

Hi Hussain,

I’m sorry for the trouble. It may help to explain the the payment date format in the events_attendee table will use the date format that is set in the WordPress>General Settings option page.

So if your accountant requires a year/month/day format, you can change it to the corresponding setting:

screenshot

You can even set custom formats by using this guide:
http://codex.wordpress.org/Formatting_Date_and_Time

Please note that if you change this now, it will only affect payment records going forward, it will not change payment records already stored in the database.
Viewing 1 reply thread

The support post ‘payment_date field in events_attendee table’ 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.

The original Forum description...

Status: closed

Updated by Josh 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server