Events Made Easy › Forums › How do I … › Just export all booking info
Tagged: CSV export, invalid date format, local environment
- This topic has 7 replies, 2 voices, and was last updated 7 years, 4 months ago by
Anonymous.
-
AuthorPosts
-
Tue 12 Jun 2018 at 13:21 #58139
Anonymous
InactiveHello Franky,
when I cklick on CSV export on events admin panel, I have only 81 records there. But that`s not all. How is it possible? How can I download complete event booking data?Thnak you,
JiriWed 13 Jun 2018 at 08:40 #58143Franky
KeymasterThe csv export (and the corresponding “printable view”) is per event, but should include all bookings for that event.
Wed 13 Jun 2018 at 09:07 #58145Anonymous
InactiveI have only one event, but CSV export is not complete. I see more registrations in the tab “Change registration” than in CSV. How can I help to debug this?
Wed 13 Jun 2018 at 11:28 #58146Franky
KeymasterSince the same code is used, that would be very surprising. But I learned to never rule out a bug. Either you try to reproduce it, or you give me a temporary admin account.
Wed 13 Jun 2018 at 12:05 #58147Anonymous
InactiveNo problem, I just sent you personal message.
Sun 17 Jun 2018 at 18:59 #58153Anonymous
InactiveIn my case export CSV stops at some row because the next row was corrupted.
This has been solved by correction of the date field in the booking form. If I understand, local environment (Czech) caused problems in validation (parsing) date values, but obviously only some of them. All the records with specific dates were corrupted, for example “27. 10. 1982”. I had to edit these specific records via “Change registration” and save them again. Then, after doin this for each broken submission, was the CSV export successfull.This is a good trick to disable date field validation by Franky:
Now the returned entry contains spaces, and those cause parsing errors.
In order to fix this once and for all, could you try to change the following in eme_functions.php, function eme_localized_date:
at around line 695, you’ll find:
$eme_date_obj = new ExpressiveDate($mydate,$eme_timezone);
change this into:try {
$eme_date_obj = new ExpressiveDate($mydate,$eme_timezone);
} catch (Exception $error) {
return $mydate;
}Then all parsing issues should just result in the date being returned as is …
SOLVED
Sun 17 Jun 2018 at 22:19 #58154Franky
KeymasterThis will be in the next version 🙂
Sun 17 Jun 2018 at 22:30 #58155Anonymous
InactiveFor sure, the bad dates using were:
21.09.1974
20.01.1977
27.10.1981
12.05.1963I don’t the key why only these dates.
Thank you Franky, EME is the best! -
AuthorPosts
- The forum ‘How do I …’ is closed to new topics and replies.