lorddev

@ishitaka

Adding the “NULL” did the trick thanks! Also – csv re-formatting date to MM/DD/YYYY was an issue – so just saving csv with date formatted as YYYY-DD-MM and leaving csv open as I import works just fine.

Probably will write a function to just re-format date after import and re-save meta.

Thanks for all the help!

No, I’ve kept the same date in both fields. I’m supplying the values for the following keys:

post_author | post_title | post_type | post_status | event_all_day | event_start_date | event_end_date | short_title | xo_event_cat

The import creates the custom posts and shows the custom fields populated with the correct data.

The issue – I have a category specific shortcode calendar on each “tour” page. These calendars do not display the associated events unless I go into each imported event and manually click the update post button.

I’m trying to make it easy for a client to update all of their arrival dates for tours they offer, editing xml would beyond frustrate them.

Besides – wouldn’t any post that existed just be skipped by WordPress stadard import?

I used simple csv/xml export plugin – which did a pretty good of showing me keys and a quick comparison in the database confirmed they’re correct.

I used Ultimate importer pro (for custom fields) to import. And it does create new events and updates the meta – but the meta data doesn’t display on the calendars…

So I’m assuming there must be additional hidden fields/data, or something different when gets submitted when clicking the update post button when editing in a post.

Does that make sense?

I mean, I have no issue doing the initial import via xml – but my client will definitely want to update the dates via a csv file.

Thank you for the quick responnse!