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

Support

Home Forums Event Espresso Premium Importing venues directly into SQL Database

Importing venues directly into SQL Database

Posted: July 26, 2013 at 5:47 am

Viewing 5 reply threads


Winston Douglas

July 26, 2013 at 5:47 am

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?


Dean

  • Support Staff

July 26, 2013 at 6:11 am

Hello Winston,

At this time we do not have an importer for venues.

ID is an incremental count, starts at 1 and goes up.

Meta is a serialised array for example:

a:6:{s:7:”contact”;s:0:””;s:5:”phone”;s:0:””;s:7:”twitter”;s:0:””;s:5:”image”;s:0:””;s:7:”website”;s:0:””;s:11:”description”;s:0:””;}

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”;}

Hope that helps!


Winston Douglas

July 26, 2013 at 6:14 am

Hi Dean, sorry rather than ID I meant the Identifier field


Dean

  • Support Staff

July 26, 2013 at 6:23 am

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:

1-xxxxxxxxxxxxx

Which is 1 dash 13 numbers/letters.


Winston Douglas

July 26, 2013 at 7:27 am

Thanks Dean.

I created the following excel formula which generates the serialised array for the meta data:

=R1&”:{s:”&LEN(L1)-2&”:”&L1&”;s:”&LEN(L2)-2&”:”&L2&”;”&”s:”&LEN(M1)-2&”:”&M1&”;s:”&LEN(M2)-2&”:”&M2&”;”&”s:”&LEN(N1)-2&”:”&N1&”;s:”&LEN(N2)-2&”:”&N2&”;”&”s:”&LEN(O1)-2&”:”&O1&”;s:”&LEN(O2)-2&”:”&O2&”;”&”s:”&LEN(P1)-2&”:”&P1&”;s:”&LEN(P2)-2&”:”&P2&”;”&”s:”&LEN(Q1)-2&”:”&Q1&”;s:”&LEN(Q2)-2&”:”&Q2&”;}”

Replace my heading cells with yours and depending whats entered into the data cells from row 2 downwards it will output:

A:6:{s:7:”Contact”;s:0:””;s:5:”Phone”;s:17:”+61 3 86 25 77 00″;s:7:”Twitter”;s:0:””;s:5:”Image”;s:75:”http://valoros.com/wp-content/uploads/2013/07/TestraDome_Stadium_Aerial.jpg”;s:7:”Website”;s:30:”http://www.telstradome.com.au/”;s:11:”Description”;s:2:”XX”;}

Empty data cells must contain “”

Just thought maybe of use to anyone who’s trying to do the same.


Dean

  • Support Staff

July 26, 2013 at 7:35 am

No problem and thanks for sharing.

Viewing 5 reply threads

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.

Event Espresso - Staging Server