CSV import broken with version 4.6.1

I’m also running into this issue with the CSV Uploader. Some items load and other just keep saying January 1, 1970

Hi. Nice to know that this is a shared issue to expect a fix soon.
Maybe a developer would be interested to know that we may also expect that the CSV importer should be able to offer to delete automatically all the actual imported events before a new file is imported. Just a checkbox “Delete all imported events before importing this new file”. So we may not have to delete manually +160 events each time we change the date of a training.

I agree–some sort of fast way of clearing events.

Is any developer able to follow up why dates appear with January 1, 1970?

I think that this forum is checked by the team on wednesday. It means that we may not have a fix this week now.

Hi.
I let you know that the CSV importation is still broken.
From the provided CSV file, the import misses one line, injects many “01 January 1970” dates and makes many events lenghts one year.
Frankly I don’t really understand where the development of this plugin is going to whereas the basics are regularly broken by updates.
See you.

Hi.
All the issues still exist with version 4.6.2.
– One event is missing (157 imported) whereas the import counts 158 usefull lines
– January 1, 1970 dates for half of the imported events
– Two days classes appear with a lenght of exactly one month
…
Any fix possible ?
Best regards?

• This reply was modified 7 years, 1 month ago by uscarsfrance.

Yes the import function does not work. All events come in as January 1, 1970. How could I even consider paying for the Event Aggregator when the unpaid version does not work and has not for quite some time.

The issue is still there in version 4.6.3. For the knowledge of the manager who is supposed to take care of the support, nothing has been done in one month. A one star review (I should say “report”) has been posted and that is a first time for me.

Hi @uscarsfrance,

I’m sorry to hear that you are experiencing this issue!

As a first step, I would recommend running through our testing for conflicts procedure and testing if your imports work properly with a minimal scenario.

I hope this helps!

@user7942, @schnazalope – if you are still experiencing issues, please open up new threads. We’d love to help you there!

• This reply was modified 7 years ago by Jaime.

Hi. As at least one guy here has the same issue and that the issue rose with a particular version of the plugin, wouldn’t have it be nice to import the file provided in the thread with your development environnement just to check ? Do you think that a plugin conflict may make a one day imported event being exactly a one month event whereas the first events provided in the sample before the importation are clearly ok ? Best regards.

Hi.
The version 4.6.4 does not fix the 4.6.x issue with the CSV import.
Here is the most basic example possible :
https://www.dropbox.com/s/l8a95zkepwodvkf/calendar-events-converted-14.csv?dl=0
2 events.
The preview of the 2 events is correct but once imported, these 2 events starts and ends January 1, 1970.
Do you still expect that it is not an issue with the plug-in ?
Best regards.

Hi.
The version 4.6.5 does not fix the 4.6.x issue with the CSV import.
Here is the most basic example possible :
https://www.dropbox.com/s/l8a95zkepwodvkf/calendar-events-converted-14.csv?dl=0
2 events.
The preview of the 2 events is correct but once imported, these 2 events start and end January 1, 1970.
The issue is reproductible on 2 different websites.
Best regards.

Hi.
The version 4.6.6 does not fix the 4.6.x issue with the CSV import.
Here is the most basic example possible :
https://www.dropbox.com/s/l8a95zkepwodvkf/calendar-events-converted-14.csv?dl=0
2 events.
The preview of the 2 events is correct but once imported, these 2 events start and end January 1, 1970.
The issue is reproductible on 2 different websites.
Best regards.

Hi,

I am not sure what changed, but I got your CSV import to work with one modification.

I changed the dates to use dashes to separate the dates so this:

23-06-2017

That is the format for using international little-endian format per our instructions under Field Types and Date:

https://theeventscalendar.com/knowledgebase/csv-files-options-and-examples/#field-types

If you use that format does it work for you?

Hi.
I improved my script to replace the “/” by a “-” in the start date and the end date columns and now, it looks like the importation is full and correct. I’m pretty sure that something has changed somewhere and at some point because the imported CSV file is the same than the one I used when I was still using version 4.5 of the plugin (but also a previous version of WordPress). Let’s consider that the topic is now closed !
Best regards.