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, Buddypress, subdomains and memberships | Event Espresso - Staging Server
Okay, so I’ve got to build a complicated website. It’s a site with health classes (events). Users whom have payed for the event should also be able to download (restricted) PDFs with course information.
On top of that, there has to be some kind of community. Ideally, buddypress.
I have some ideas on how to achieve this but I could really use some advice from the experts :)
Then another question. If I have 2 subdomains I want to install EE on, will I need to purchase the plugin twice?
I need to know because the on the same website, there will also be courses (using EE) available for the coaches whom will be running the health classes. I’m playing with the idea of creating a main site (example.com) for the general users, and a subdomain for the coaches (coaching.example.com).
I’ve actually come up with a solution. I will be building a private buddypress site with members-only restricted content (where members can download pdfs). Only users with an invitation code will be able to register. They will get their invitation codes at the health classes (they can sign up with EE). This way EE doesn’t need to integrate with buddypress.
That leaves one question. Will I need to purchase EE twice if I want to install it on 2 subdomains?
The support post ‘EE, Buddypress, subdomains and memberships’ 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.