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
Event Espresso and Multisite | Event Espresso - Staging Server

Support

Home › Forums › Translations › Event Espresso and Multisite

Event Espresso and Multisite

Posted: January 24, 2014 at 2:34 pm

Viewing 1 reply thread


Mark Christoffersen

January 24, 2014 at 2:34 pm

Will EE work a WordPress Multisite configuration? I am putting together a couple of sites which will need event registration. I like this product, but conserned on the Multisite limitations. If it works, what type of licensing will I need? All I need is the Personal license, but wasn’t sure how the linsing worked on Multisite (if it works).

Thanks


Garth

  • Support Staff

    •

January 24, 2014 at 3:31 pm

Hi Mark,

There are several reasons we’d not recommend using Event Espresso 3 in a MS configuration. MS installs are often overly complex for most projects (just our observation), so just be careful. But in general you can’t network activate it and you’ll have to manage updates manually e.g. download, deactivate, delete, upload, and activate.

Does that make sense?
Viewing 1 reply thread

The support post ‘Event Espresso and Multisite’ 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.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Garth 10 years, 12 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server