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 Importing venues directly into SQL Database | Event Espresso - Staging Server
I’m using Sequel Pro to try and import all my venues directly into the EE WP_EVENTS_VENUE Table. I see an ID Field and Meta field. How are these fields populated? Is there a way to populate them while importing from CSV?
it stores all the extra bits of information. Here is one filled out:
a:6:{s:7:”contact”;s:4:”Dean”;s:5:”phone”;s:12:”01234 567890″;s:7:”twitter”;s:14:”@eventespresso”;s:5:”image”;s:37:”http://www.fakesite.com/fakeimage.jpg”;s:7:”website”;s:21:”www.eventespresso.com”;s:11:”description”;s:35:”This is a description for the venue”;}
The identifier is a randomly generated unique code for the venue (events and attendees also have their own ones too). You can pretty much use anything here so long as its unique, though I recommend following the format:
The support post ‘Importing venues directly into SQL Database’ 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.