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
Issues with *_attendee_cost table | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Lite › Issues with *_attendee_cost table

Issues with *_attendee_cost table

Posted: January 31, 2013 at 1:23 am

Viewing 2 reply threads


Nico Loubser

January 31, 2013 at 1:23 am

Hi

Does anyone know whether EventEspresso has dropped the *_attendee_table from their DB install? I have been having problems with clients whose *_attendee_table tables are non existant after an install.

Thank you,

Nico Loubser


Dean

  • Support Staff

    •

January 31, 2013 at 1:40 am

Hello Nico,

The attendee_cost table is no longer in existence since 3.1.28 and I believe wasnt in use by the plugin for several versions before that.

You can use a great plugin called Adminer to check what tables are available.

Generally if the tables dont exist after install/update a bad install occurred, you can try deactivating and reactivating the plugin to make it create the tables it needs.


Nico Loubser

January 31, 2013 at 1:43 am

Thank you for clearing that up, Dean.

Nico
Viewing 2 reply threads

The support post ‘Issues with *_attendee_cost 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.

Community-based support for the free version of Event Espresso.

Status: closed

Updated by Nico Loubser 11 years, 11 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server