Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Venue ID for Event Imports | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Venue ID for Event Imports

Venue ID for Event Imports

Posted: October 1, 2013 at 1:08 pm

Viewing 3 reply threads


Deborah Walden

October 1, 2013 at 1:08 pm

Hi All,

I have all my venues pre-populated in my system. Is there anything on the horizon that will let you enter a venue id in the CSV which then uses the data already in the DB upon creation of your new event? Many of our venues have secondary address lines, i.e. STE. 112. and there is no column header for a second address line in the current events.csv file.

Is is possible to just add the table name into the CSV? I haven’t checked, but something like address_2? Thanks!


Dean

  • Support Staff

    •

October 2, 2013 at 2:17 am

Hi,

At this time we have no plans for adding in venue support to the event import spreadsheet.

I will certainly add your request to our feature request list.


Deborah Walden

October 2, 2013 at 11:06 am

Hi Dean,

Yes please see if we can get that one on the board. I believe the addition of being able to add venue support and detail which question groups to use on the import would really make bulk event management a serious force in Event Espresso.


Dean

  • Support Staff

    •

October 3, 2013 at 12:55 am

No problem, I marked down your ideas on our list.
Viewing 3 reply threads

The support post ‘Venue ID for Event Imports’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Dean 11 years, 3 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server