Plugin Support
Darian
(@d0153)
Hi @damiensw
Thanks for reaching out. Let me help you with this one.
I understand that it can be frustrating when some events don’t get imported. Have you checked if any of the events have the same name as those that were successfully imported? If so, you can give them temporary names like event1, event2, etc. This should help with the import process. You can always rename them later to their correct names.
When it comes to the location of the event, it’s recommended to either import or create the venue beforehand. After that, you can import your events and indicate the specific name of the venue that you’ve already added/imported. [see CSV format for venues]
I hope this helps, and please let me know if you have further questions or concerns.
Hello Darian, thanks for your answer.
Unfortunately, it didn’t help for dates, only 6 seems to be well imported.
Maybe it’s relative to date format, but it seems to be well configured.
Here is the original sheet, with new names (-2, -3 after repeated names) :
https://snipboard.io/C9wyOt.jpg
Here is the result after importation :
https://snipboard.io/LlbkA2.jpg
I realize maybe it’s because the system consider date as m/d/Y, but my settings are d/m/Y in wordpress settings, AND in event calendar settings :
https://snipboard.io/4DeNrB.jpg
https://snipboard.io/3nThVR.jpg
Maybe this is the key, but still, my client would like to be able to import their calendar with original format. Even names, they can repeat sometimes, is there a way to avoid to rename them ?
Thanks very much for your help
Plugin Support
Darian
(@d0153)
Hi @damiensw
Thanks for your response.
We understand the importance of having a properly formatted CSV file and we’re here to help. Our knowledgebase article outlines the appropriate formats for each column, which can be a great resource for ensuring your file is correctly formatted. We do want to note that the date format should be Y/m/d.
As for the events with the same title, we’re already aware of some issues with this, and we want to assure you that we’re actively working on a solution. While we don’t have a specific timeline for the fix, we’ll keep you updated through this thread.
Let me know if you have other questions or concerns.
—
Internal Bug Ticket Reference: TEC-3875