The wordpress.org infrastructure work ha…

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

The wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ infrastructure work has reminded me how much I dislike having the Super Adminadmin (and super admin)/Networknetwork (versus site, blog) Admin pages appearing alongside the regular per-blogblog (versus network, site) admin pages. I think the Super Admin menu should go away, away to a separate network admin area. Ticket 14435 is where I’m scratching this itch. The patches there move the network admin pages to wp-admin/network/. It is a completely separate admin area just for network management. It is available only from the main site url. Visiting wp-admin/network from other blogs in the network will redirect to the one true place. If you have multiple networks, they each will have a network admin area.

While I was in there I added a network plugins.php. Network activations and deactivations happen here and only here. Network activate/deactivate is no longer available from the blog admins.

Thoughts?

#multisite, #network

Jane Wells 12:17 am on July 28, 2010

Agreed. We can brush up the UIUI User interface for these screens in 3.1.
Alex M. 12:21 am on July 28, 2010

Sounds good to me and will make it less confusing.
John Blackbourn 12:22 am on July 28, 2010

This bugs me too, and is especially confusing when you’re on the networknetwork (versus site, blog) adminadmin (and super admin) page but everything else is telling you you’re in the admin area for a member blogblog (versus network, site). +1
John Blackbourn 12:25 am on July 28, 2010

Off-topic: Why is this post tagged with ‘multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site’ and ‘networknetwork (versus site, blog)’ yet only the ‘multisite’ tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) is clickable? (Underneath Ryan’s name at the top.)
- Ryan Boren 12:29 am on July 28, 2010
  
  I think because this is the only post in that tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.).
- Alex M. 12:30 am on July 28, 2010
  
  It’s only clickable if there are other posts with that tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). Note the “(3)” following “multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site” — that’s how many posts there are with that tag.
  
  EDIT: Bah, too slow! 🙂
Lloyd Budd 4:18 pm on July 28, 2010

I like this.
I’m a little hesitant of “It is available only from the main site url.” Super/Networknetwork (versus site, blog) adminadmin (and super admin) being able to be in the context of the current blogblog (versus network, site) is very handy. It saves a lot of extra text entry and clicks having to look up a blog.

I think there are benefits of making it blatant that one is logged in as a super admin. It’s a good reminder not to be 😉
- Ryan Boren 4:50 pm on July 28, 2010
  
  There are definitely some work flow advantages to allowing networknetwork (versus site, blog) adminadmin (and super admin) to be in the context of the current blogblog (versus network, site). Things like being able to “Add user to current blog” from network/users.php would be nice. We need to document some common work flows and see how best to accommodate them.
- Ryan Boren 4:58 pm on July 28, 2010
  
  Other things to consider. Make the Networknetwork (versus site, blog) Adminadmin (and super admin) link sensitive to context. Link to network/themes.php if on themes page. Link to site editor if on other pages. Or, add an action to Favorite Actions for super admins.
- Ron 5:00 pm on July 28, 2010
  
  From a workflow perspective, I agree with Lloyd. I was going to suggest using context variables, but I see Ryan beat me to it 😀
  - Ryan Boren 7:56 pm on July 30, 2010
    
    I added some code to save the blogblog (versus network, site) ID for the last blog adminadmin (and super admin) area visited. This allows linking back to that blog from the networknetwork (versus site, blog) admin. Just an experiment. I really like having a canonical network admin and this is an attempt to have it both ways. 🙂

Comments are closed.

Welcome!

Communication

Share this: