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 Batch Import Tool Not Working - File not found. | Event Espresso - Staging Server
Thanks for the Import Tool – It worked great the first time I imported attendees. I just tried to import another group of attendees and here is what I’m getting:
In a yellow box – File uploaded successfully. – events.csv
directly below yellow box there is a red box that says: File not found. Make sure you specified the correct path.
When I rename the file attendees.csv it says everything was successful and 275 attendees have been added but when I go to the attendee list, the attendees I added are not in the list.
As per the instructions “The file name should be events.csv in order for it to work.” SO thats why the attendee.csv isnt working.
Now, why it gave the red error Im not sure, is the file structure the same as the last one you used? Has the file been saved as a CSV correctly? If you are using Microsoft Excel, I find it really useful to paste the contents into a Google Docs Spreadsheet and save that file as a CSV, as Excel really doesnt handle CSV files correctly.
Viewing 1 reply thread
The support post ‘Attendee Batch Import Tool Not Working – File not found.’ 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.