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
Attendee Import 0.1 Working, but instructions need to be updated | Event Espresso - Staging Server

Support

Home › Forums › Pre-Releases › Attendee Import 0.1 Working, but instructions need to be updated

Attendee Import 0.1 Working, but instructions need to be updated

Posted: September 14, 2013 at 1:05 pm

Viewing 6 reply threads


Robert Lansing

September 14, 2013 at 1:05 pm

Hello,
Just a follow up to the previous confusion. I attempted to import attendees with an “events.csv,” but I received both success and file not found notifications. This is because in the code, it references $csvfile = "../wp-content/uploads/espresso/attendees.csv";
Obviously in the future it will be easier to accept whatever file name is on the csv, but in the meantime there should be some clarity as to what the filename must be to get this to work. I received only successful notifications after renaming my file to “attendees.csv.”
As well, the import looks great.
Thanks for a great improvement!
Bobby


Robert Lansing

September 14, 2013 at 1:18 pm

Correction: The import function worked for the first 98 lines on my CSV of 107 “rows”. For some reason the last 8 attendees were not uploaded. Still a huge time saver.


Dean

  • Support Staff

    •

September 15, 2013 at 7:58 am

Hi Robert, thanks for the feedback, I have added some tickets to that code base to look into those issues.


Robert Lansing

September 15, 2013 at 11:57 am

I apologize, it was my error. I did not notice that only 50 attendees were being downloaded from the database at a time. Once I selected to display “all” attendees from the database they all showed up indicating a flawless import. I would recommend that this option be set to 100 or all by default. But that is my preference. Sorry for the added work…


Dean

  • Support Staff

    •

September 16, 2013 at 12:53 am

No problem, I’ll remove that ticket. The attendees.csv is still a good catch though!


Robert Lansing

September 16, 2013 at 10:52 pm

Another issue I encountered was after import, the attendees I imported could not be updated with regards to payment status specifically. This was due to the “is_primary” field default to “0”. I went into mySQL table “bwt_event_attendee” and set the value to “1” for these contacts specifically. Afterwards all imported contact’s payment status was updatable.
Thanks again,
Bobby


Dean

  • Support Staff

    •

September 17, 2013 at 2:33 am

Noted, thanks.
Viewing 6 reply threads

The support post ‘Attendee Import 0.1 Working, but instructions need to be updated’ 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.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Dean 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server