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
Multiples sites, single EE instance | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Multiples sites, single EE instance

Multiples sites, single EE instance

Posted: June 5, 2013 at 10:50 am

Viewing 1 reply thread


Ahmed Selim

June 5, 2013 at 10:50 am

I am working on a project where I will have one main site lets call it mainsite.com as well as other sub sites (for marketing purposes) offering specific events….

My intent is to use my mainsite.com  as my registration site, meaning when someone is interested in registering for an event they will use mainsite.com.

I am trying to figure out if it is possible to have the my sub-sites list the events, from mainsite.com (based on category etc) and when someone wants to register, then redirect to registration for that specific event?

Is this possible?  If so, then how and is there anyone who has already done this?


Garth

  • Support Staff

    •

June 5, 2013 at 11:43 am

Hi Ahmed,

How are you today?

You’d have to use custom programming to pull the event listings from your registration site into the sub sites. You could use the custom queries or the JSON API to list the events (again custom programming).

I’ve never heard of this done, but that doesn’t mean it hasn’t been done.
Viewing 1 reply thread

The support post ‘Multiples sites, single EE instance’ 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.

Status: closed

Updated by Garth 11 years, 7 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server