|
coh
|
March 26, 2015 at 4:37 pm
Dear Support,
We have recently upgraded to EE4 (now running 4.6.18.p) and saw that the Import feature has been temporarily disabled. Any idea when this will be resolved?
If there is a temporary work around, please let me know as we have to import 70+ events for our client and would prefer not to manually key them in.
Thanks in advance!
Chin..
|
|
Dean
|
March 27, 2015 at 2:29 am
Hi,
Due to the “under the hood” complexity of EE4 events, we are still working out the best way (and most user friendly way) to allow imports. I can’t give a timescale on when the feature will return, but it is being worked on.
|
|
coh
|
March 27, 2015 at 6:26 am
Dean, thanks for the quick response and update.
|
|
SafetyTrainer
|
April 7, 2015 at 2:37 pm
Hi Dean,
I’m in the same boat. I have a deadline coming up. Please let me know whether this fix is still a priority. Or send me the “work around” if there you sent one to CHO.
I’m going to have to start manually entering events very soon. Thanks Mo
|
|
Josh
|
April 7, 2015 at 3:19 pm
Hi there,
It turns out it’s a priority, however, the import feature isn’t really intended for automatic/bulk event entry. The import feature was built for copying events from one site to another (machine to machine). It wasn’t designed to be used as something where someone input rows into a table and bulk imports the events.
If you have a lot of the same features for events and want to speed up the entry/simplify adding events, there are filters you can use to set the defaults. Here’s a guide in the developer portal that outlines how:
http://developer.eventespresso.com/docs/modifying-the-defaults-on-creating-a-new-event/
|
