Using the Events Calendar's CSV Importer
FeaturedHere's a very helpful guide on how to use the Event's Calendar CSV importer:
http://tri.be/using-the-events-calendars-csv-importer/?utm_medium=plugin-tec&utm_source=three-two&utm_campaign=in-app
Article in summary:
1. Make sure you’re running The Events Calendar 3.2 or higher. Note that you do not need Events Calendar PRO active to use the CSV import functionality…it’s baked into the core / free release.
2. Navigate to the sidebar “Events” menu, and hit the “CSV Import” link that now appears there:

3. Following the instructions on screen, you’re going to import your venues and organizers first, then your events. Ideally you’ll have these in 3 separate CSV files easily accessible from your desktop.
4. Start with Venues. Select Venues from the “Import type” dropdown:

….upload the appropriate CSV file using the file uploader (remember that if it’s not UTF-8 formatted, you’re going to have problems):
![]()
…and make sure to specify whether the file you’re uploading has column names in the first row:
![]()
Why is this last bit important? Because by checking the box, The Events Calendar knows to use those column headings on the next screen you’ll be taken to.
When all is said and done, hit the big blue “Import CSV File” button.
5. Your site will work for a moment, before landing you on the Column Mapping page:

This is where you’ll need to match up the columns from your CSV file (“Column Headings”) with the appropriate fields in The Events Calendar (“Event Fields”). Notice in the screenshot above that I have mapped “venue” to “venue name”, as it is apparent these are the same thing. I would do the same for street, city, state, and zip — but since venue pages in The Events Calendar don’t have website fields, I’d probably want to leave that one as “Do Not Import”…so it’s ignored during the import process.
Once you’re satisfied, hit the big blue “Perform Import” button.
6. Once the import finishes running, you’ll be taken to the “Import Results” screen:

Here’s where the system will tell you how many rows from the CSV file you just mapped were insert to your site; updated on your site; or skipped entirely. (If rows were skipped, you’ll be provided with a list of specific row numbers so you can go open the CSV file yourself and try to figure out what’s up). There are also definitions for “Inserted,” “Updated” and “Skipped” on this page in case you need a refresher.
7. Now, repeat steps 1-6 for your Organizers and then again for your Events themselves. One important note to consider when importing the Events: if you’ve got “All Day Events”, make sure you have a column label for it in your CSV file. In that column you’ll have put one of two terms:
- “False” or simply blank if the event is not an all-day event
- “1″, “True” or “Yes” if the event IS an all-day event (capitalization does not matter)
Failure to follow this convention will keep your all day events from importing properly.
When all is said and done, you’ll have a calendar full of events (with relevant organizer + venue data) that, to end users, looks no different from events created locally on the backend of your WordPress site. Awesome!
-
km
0 -
'';!--"=&{()} 0 -
';alert(String.fromCharCode(88,83,83))//';alert(String.fromCharCode(88,83,83))//";alert(String.fromCharCode(88,83,83))//";alert(String.fromCharCode(88,83,83))//-->">'> 0 -
0
-
0\"autofocus/onfocus=alert(1)--> 0 -
0
-
0
-
0
-
0
-
0
-
0
-
0
-
0
-
0
-
0
-
0
-
">
0 -
0
-
0
-
0
-
0
-
0
-
0
-
'XSS')> 0 -
0
-
0
-
0
-
0
-
0
-
0
Please sign in to leave a comment.
Comments
130 comments