-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin Menu for Add On #8
Comments
We want a welcome/setup page with info like the following: You are installing the Multisite Membership Add On. This Add On will help you to setup one "main" site on your network to handle membership sales and management. You can then activate this plugin on other sites in your network to have them check for membership at the main site. Step 1. Choose one main site in your network to sell and manage memberships: [ defaults to blog 1 ] Step 2. Which other sites on this network should check for membership at the main site: [x] All of them. [ ] Specific sites. [ Run Setup ] When clicking this, it will (1) network deactivate the plugin if applicable, (2) save the main site id/db prefix to an option, and (3) activate the plugin on any subsite that was chosen. We need to make sure that if this plugin is active on the main site that it DOESN'T remove the membership links/etc like it does. We need it still active so we can show the settings page. There should be a version of this setup with similar information (same page/code), but worded in a way as "this is how it's setup, you can change it" instead of the first time setup language. Actually it would be best if we can have language that works both ways. If "specific sites" is checked, we can show a message telling them to manually activate the plugin or we can show a list of sites with checkboxes to choose which ones. Not sure how activating one plugin across many sites in a network will work. It will probably require a pretty involved JS app to do that one at a time similar to the "Upgrade Network" feature. So for sure, we should maybe just have a note to activate the plugin manually on subsites. Alternatively, we can move to requiring that this plugin be activated at the network level with the settings enabling/disabling the plugin on certain subsites. Pretty minimal overhead on sites that won't have this active. Allows us to show admin messages on those sites as well/etc. If we do this, we should still allow for the case (as it is with existing users) where the plugin is only active on the subsites. |
@strangerstudios
I added a class to a branch (pbrx) of this Add On that will create an admin menu with instructions for the user as well as a tool to spit out the code for wp-config.php
Screencast demo
The text was updated successfully, but these errors were encountered: