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
EE database and sub domains | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › EE database and sub domains

EE database and sub domains

Posted: April 17, 2014 at 6:35 am

Viewing 2 reply threads


poumonAPQ

April 17, 2014 at 6:35 am

hello,
I just need some information about the EE database. I have version 3 installed on a wordpress multisite program. I have 4 sub domains which all have EE setup in them. For each of these subdomains I have setup EE events, one sub might have 2 events, another just 1 and so on…
My question is simply: are all the events in the subdomains inside 1 database? or are they spread out in their own database? I kind of assume that since subdomains are just virtual and there is only 1 version of EE inside one version of WP that the events are inside 1 db only. I just need to confirm this. thanks


Lorenzo Orlando Caum

  • Support Staff

    •

April 17, 2014 at 12:07 pm

Hello,

According to what you have described with your WP multisite setup, each subdomain should be in the same database but each site will have a different dbprefix.

Are you seeing something different if you look at the database using a tool like PHPMyAdmin?

—
Lorenzo


poumonAPQ

April 22, 2014 at 11:47 am

actually I hadn’t looked there, but looking at it now, it’s fine. thanks
Viewing 2 reply threads

The support post ‘EE database and sub domains’ 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 poumonAPQ 10 years, 9 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server