Network-wide Stream
shadyvb opened this issue · comments
- Add an option to Stream to make it network-wide
- Add option to disable Stream admin on individual sites
- Add individual site settings as a tab on the network site settings
- Add blogs connector to log blog creation an administration actions
- Storing records in a single table, with site_id/blog_id
- Showing Stream widget in the Network Admin dashboard ( Relates to #13 )
/cc @blobaugh
Be sure to note that site_id and blog_id are completely different. The site_id refers to the network, the blog_id refers to the site. I know, confusing isn't it? ;)
Basically when you create a multisite it sets up a default network of blogs, however you can also create any number of additional networks that will each have their own network admins and own blogs. It is like running several seperate multisites off the same WP install.
I am probably blowing hot air though cause you smart people already know that :)
http://nacin.com/2010/03/25/terminology-nightmare-blogs-sites-networks/
@blobaugh Many thanks for the link! Actually the first prototype of Stream had table fields for site_id (only) to test the network-wide ability of this. But due to the project schedule it was postponed since making the plugin network-wide would need some tweaks to how we store/grab options, as the article shows.
Thanks again for the tip :)
Tossing in a lazy 👍 for all of this so far. I can see using this extensively in the WSUWP Platform project, so happy to test and help where needed.
It is very important that this feature gets thoroughly tested with various multisite configurations before it is release ready. To help beta test the network-wide functionality you can do so by cloning the repository as outlined in contributing.md .
Checkout Feature Branch
To checkout and use the network-wide feature branch:
git fetch upstream
git checkout issue-65
git pull upstream issue-65
To follow progress see: #154
Usage:
You an activate the plugin separately for any site on the network. You can also network activate. When you network activate the master stream administration screen is found in the network admin.
@c3mdigital what kinds of negative impacts should we be watching for? Could this damage a site, or merely get stream data mixed up?
@topher1kenobe Mainly just look for errors in the logging on the network admin and individual sites. There is no danger of damaging a site just the possibility of messing up the stream data.
To allow for this point "Add individual site settings as a tab on the network site settings" this patch for core https://core.trac.wordpress.org/ticket/15800 would be pretty useful. Don't you think?
@cfoellmann When I realized there was no way to add tabs I was going to create a ticket until I found the one you referenced. I've made pretty good progress on a patch but it's a pretty complex issue.
@c3mdigital what is you idea on how to tackle this? Have a look at this cfoellmann/WordPress#3 to see how I think it could be done.
@cfoellmann Just added the patch I was working on to the ticket.
Progress Update on Network Wide Stream:
Unfortunately the settings API does not work in the network administration. For network wide settings this is requiring writing a wrapper that manually saves $_POST data for network wide options. For managing the individual sites, I'm adding a select field with all the blogs on the network then firing switch_to_blog so the settings for each site can be managed by the network administrator.
Look for a code update this weekend.
@c3mdigital Thanks for the update on this. We'll be on the look out.
Closed by #401 .
@jeremyfelt Just circling back around to your note above about testing (finally). We're now multisite compat as of 1.4.0, would love to hear any feedback/input you might have for us. A full code review would be really awesome! 😉
/cc @lukecarbis