﻿__group__	ticket	summary	owner	component	_version	priority	severity	milestone	type	_status	workflow	_created	modified	_description	_reporter
Commit Candidates	22277	Admin (not just superadmin) should be able to add user without confirmation email in multisite		Multisite	3.4.2	normal	normal	3.6	defect (bug)	new	commit	2012-10-25T18:04:19Z	2013-05-02T00:48:36Z	I don't know why admins would be restricted from adding existing users without sending them a confirmation, but they are in multisite. You have to be a superadmin to get that option. I think that is lame, and would like to see admins have that admin option. Is there is a reason why it is that way (security etc)? Since neither @markjaquith nor I could remember a reason, making this ticket and hoping we fix it. 	jane
Commit Candidates	20220	add test to see if sunrise === on in ms-settings		Multisite	3.0	normal	normal	Future Release	enhancement	new	commit	2012-03-12T19:06:56Z	2012-11-02T22:49:31Z	"We needed to disable sunrise for certain requests. 

We thought about declaring sunrise before including wp-load, but setting it to 'off'. Then having a conditial in the wp-config that only defines it to on if it is not defined and then in ms-settings to a additional check to see if sunrise is defined and equal to on. (the patch I am adding does not have the wp-config if !defined() as wp-config doesn't get updated, but if someone feels it is helpful I can add it)

Others could of changed the default defined value of sunrise and this could break bc. I am therefore not sure if the limited use case warrants it. But I thought I would suggest it."	sboisvert
Needs Dev / Bug Wrangler Feedback	19686	404 - File or directory not found		Multisite	3.3	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-12-29T19:47:45Z	2012-01-03T21:38:51Z	"We are running Wordpress using multiuser with Buddypress. Users are getting the 404 error after they click the save button in their settings.

I'm opening this ticket to report the source of the problem.

Wordpress 3.x
Buddypress 1.5
Windows 2008 R2 (IIS 7.5)

Themes installed are all Buddypress compatible and all themes seem to be affected. 
All option pages are affected.
Settings are updated when the user returns to the page - despite the error. A screen shot of the error can be seen at http://blogs.cnc.bc.ca/gagel/?attachment_id=38

The source of the problem appears to be in the wp_get_referer() function on line 164 in options.php. With the variables passed to the function it should redirect the user to the page they just submitted when they updated options. Instead they get the 404 error.

The page they're redirected to appears to be the absolute path of the submitted page appended to the absolute path again (minus the domain). So it looks like this:
userblog/wp-admin/userblog/wp-admin/options-general.php?settings-updated=true

When I switch out the wp_get_referrer() function with the variable $parent_page then the redirect worked as expected.

I'm uncertain about leaving it like this as my change may have introduced issues elsewhere...

This issue is discussed at http://wordpress.org/support/topic/recuring-404-file-or-directory-not-found-error?replies=8#post-2527566"	kwgagel
Needs Dev / Bug Wrangler Feedback	14539	Cache-Control / Expires headers not applied to files in Multisite files location		Multisite	3.0.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2010-08-05T04:21:33Z	2012-09-19T16:02:17Z	"First reported in Multisite forum and detailed there:

[http://wordpress.org/support/topic/cache-control-headers-and-uploaded-files-not?replies=5]

These file type accesses should return 304s according to the rules in .htaccess but consistently return 200, showing an incorrect Cache-Control header specification, instead of no specification at all--which is still undesired.

This occurs in two 3.0.1 Multisite installs on all blogs, domain mapped or not, but does not occur on any other domains on the server or in any other file locations in the WP tree (themes, etc.).

Initially, it was image files that I had identified this on but a subsequent check of a CSS file in the files/ location returned the same header that is set for (.php|.pl|.cgi) files; same as the image files do.

Apache 2.2.15, PHP 5.2.13, FreeBSD 7.2-STABLE, MySQL 5.0.90
"	spherical
Needs Dev / Bug Wrangler Feedback	18242	Changing domain for a network blog make faulty changes in database		Multisite	3.0	normal	major	Future Release	defect (bug)	new	dev-feedback	2011-07-25T11:33:51Z	2012-11-20T11:49:53Z	"When changing the domain for a network blog, if the network is set up on a subdomain and using sub-folder options for blogs, the save to the database is faulty, saving wrong urls.

The network main site uses eg http://my.blog.com and the blogs has http://my.blog.com/blog1

When changing the domain for blog1 in ""Network admin -> All Sites -> Edit blog1"" and choose to also update ""home and siteurl"" the new url for home and site become http://blog.com/blog1/my

Happens in both Firefox 5 and Safari 5.1"	darkwhispering
Needs Dev / Bug Wrangler Feedback	15943	Custom Post Type not set after customizing permalinks.	sterlo*	Multisite	3.0.3	normal	critical	Future Release	defect (bug)	accepted	dev-feedback	2010-12-21T23:42:55Z	2011-01-06T23:11:07Z	"Developing a plugin,

It sets a custom post type on init:
{{{
      register_post_type(
        'staff_listing',
        array(
          'labels' => array(
            'name' => 'Staff Listings',
            'add_new_item' => 'Add a Staff Member',
            'new_item' => 'Staff Member',
            'add_new' => 'Add a Staff Member',
            'singular_name' => 'Staff Member'
          ),  
          'public' => true,
          'publicly_queryable' => true,
          'show_in_nav_menus'  => false,
          'exclude_from_search' => false,
          'show_ui' => true, 
          'hierarchical' => false,
          'rewrite' => array(
            'slug' => 'staff',
            'with_front' => false
          ),  
          'query_var' => 'staff', 
          'supports' => array(
            'title',
            'editor',
            'thumbnail',
            'comments',
            'revisions'
          )   
        )   
      ); 
}}}

If I add a staff member called ""john doe"" and then go to that on the front end - I expect to see this in $wp_query->query_vars:
{{{
[staff] => john-doe
[post_type] => staff_listing
[category_name] =>
[name] => john-doe
[is_404] =>
[queried_object_id] => ###
}}}

(I replaced the ID with ### since it changes from one install to the other)

That '''works''' on a standard WordPress 3.0.3 install.

But does '''not work''' on a WordPress 3.0.3 MU install.

The MU install gives me this:
{{{
[name] => john-doe
[post_type] => 
[category_name] => staff
[is_404] => 1
[is_singular] => 
[queried_object_id] => 0
}}}

Both the permalinks on the MU and standard setup are set as follows:
{{{
/%category%/%postname%/
}}}

If I change the permalink structure on the MU site to the default structure - the problem goes away.

The new URL is: ?staff=john-doe and it sets the following:
{{{
[staff] => john-doe
[post_type] => staff_listing
[name] => john-doe
[category_name] =>
[is_404] =>
[queried_object_id] => ###
}}}"	sterlo
Needs Dev / Bug Wrangler Feedback	14873	HTTPS related issue with ms-settings.php		Multisite	2.9	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-09-14T18:23:26Z	2012-09-13T23:13:22Z	"ms-settings.php hard-codes ""http://"" in a few places.  This didn't impact me, but I can see that it might impact someone.  

Hopefully, a developer can take a look at the code and verify that, in fact, it has to change.  Seems like it does since hard-coding ""http:"" isn't a good practice, but I don't want to claim it since I haven't seen the need for it personally.

Here's the updated code that needs to replace the code in ms-settings.php starting at line 83 and ending at line 105:
{{{
        $protocol = is_ssl() ? 'https://' : 'http://';

        if ( ! defined( 'WP_INSTALLING' ) && is_subdomain_install() && ! is_object( $current_blog ) ) {
                if ( defined( 'NOBLOGREDIRECT' ) ) {
                        $destination = NOBLOGREDIRECT;
                        if ( '%siteurl%' == $destination )
                                $destination = $protocol . $current_site->domain . $current_site->path;
                } else {
                        $destination = $protocol . $current_site->domain . $current_site->path . 'wp-signup.php?new=' . str_replace( '.' . $current_site->domain, '', $domain );
                }
                header( 'Location: ' . $destination );
                die();
        }

        if ( ! defined( 'WP_INSTALLING' ) ) {
                if ( $current_site && ! $current_blog ) {
                        if ( $current_site->domain != $_SERVER[ 'HTTP_HOST' ] ) {
                                header( 'Location: ' . $protocol . $current_site->domain . $current_site->path );
                                exit;
                        }
                        $current_blog = get_blog_details( array( 'domain' => $current_site->domain, 'path' => $current_site->path ), false );
                }
                if ( ! $current_blog || ! $current_site )
                        ms_not_installed();
        }
}}} "	mareck
Needs Dev / Bug Wrangler Feedback	15936	IPv6 literal support in multisite broken		Multisite	3.0.3	normal	major	Future Release	defect (bug)	new	dev-feedback	2010-12-21T16:00:25Z	2013-02-02T06:32:22Z	"The logic for handling explicit port numbers in wp-includes/ms-settings.php is confused by IPv6 literal addresses in URLs as defined by RFC 2732.
It tries to handle the URL as it as if there were a port appended, but then fails to strip it off. Incidentally the error message here: 'Multisite only works without the port number in the URL.' is untrue, since ports are handled (but for only two particular cases, port 80 and 443).

The attached patch, against Wordpress 3.0.3, fixes both these issues, and allows ports other than 80 and 443 to be used with Wordpress, by just stripping off the trailing port rather than special-casing the two well-known ports, and not incorrectly detecting IPv6 literals as URLs with ports in. It also has the advantage of being much more compact.

It may be worth someone thinking through whether the substitution is strictly correct with reference to the URL standards, but I'm pretty sure that this is an improvement on the current code.

Thanks,
Dominic."	jmdh
Needs Dev / Bug Wrangler Feedback	16293	In multisite installs, users with id 1 or 2 can't be deleted		Multisite	3.1	normal	normal	Future Release	defect (bug)	reopened	dev-feedback	2011-01-19T00:21:34Z	2013-04-25T15:15:19Z	"You can't delete a user with user id of 1 or 2. 
See: source:trunk/wp-admin/network/edit.php@17326#L359"	PeteMall
Needs Dev / Bug Wrangler Feedback	16609	"Misleading ""Error establishing a database connection"""		Multisite	3.0.5	normal	minor	Awaiting Review	defect (bug)	new	dev-feedback	2011-02-21T17:31:10Z	2011-02-21T17:31:10Z	"Multisite install shows:

""Error establishing a database connection""

Even if credentials are OK when it doesn't find the domain entry in wp_blogs table, this is very misleading, would be helpful to have the same meaningful error message that /wp-admin shows.

I posted this problem originally at http://wordpress.org/support/topic/misleading-error-establishing-a-database-connection"	roberto.carvajal
Needs Dev / Bug Wrangler Feedback	20104	Show network-activated plugins on site plugins screen		Multisite		normal	normal	Future Release	defect (bug)	new	dev-feedback	2012-02-22T22:05:35Z	2012-08-18T22:07:03Z	"Per http://wpdevel.wordpress.com/2011/12/23/core-team-meetup-recap-multisite/, one action item is:

> Include network activated plugins in the plugins menu and give message that it is automatically on for the whole network (if admin/have rights to see plugins screen).

To enable the plugins screen for a network, a super admin can go to network/settings.php and enable the menu.

Network-activated plugins should still show on this screen to site administrators. (They just can't activate them.) This should require a few tweaks to the plugins list table."	nacin
Needs Dev / Bug Wrangler Feedback	23865	Trailing slash is not enforced when editing the path for a subdirectory site in multisite		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new	needs-unit-tests	2013-03-26T19:53:23Z	2013-04-01T09:38:28Z	"It is possible to edit an existing subdirectory site so that the path does not end in a trailing slash, this causes the subdirectory site in question to have an inaccessible home URL.

To reproduce:

 * Create a multisite network in subdirectory mode
 * Create a new subdirectory site
 * Visit the subdirectory site successfully
 * Edit the site to change the path so there is no trailing slash
 * You should be unable to visit the subdirectory site now"	simonwheatley
Needs Dev / Bug Wrangler Feedback	18043	Uploaded images dissapear after loading if using compression w/Apache		Multisite	3.2.1	normal	major	3.6	defect (bug)	new	dev-feedback	2011-07-08T22:49:15Z	2013-05-10T03:05:25Z	"I have found an issue between WordPress (Multisite) + Google Chrome (Mac) which I think appeared on my sever when I enabled compression a few months ago, but could never reproduce because it only happens with images managed by a Multisite WordPress install, not static images.

With images that are static Apache sends the file and calculates the Content-Length its self so these images work fine but if you access a file uploaded to WordPress it uses the .htaccess redirect so the image requests are sent via ms-files.php for what ever reason.

The problem is that WordPress decides to calculate its own Content-Length header in the HTTP Response which means that security conscious browsers like Google Chrome freak out when the data they receive is less than they we're told by Apache and they resultantly disable the image.

The Content-Length calculation comes on line 43 of ms-files.php I don't know why its needed because Apache seems to sort it out automatically if you don't send your own header, in fact most of the file seems like an unnessisary load of processing, perhaps it needs reviewing but this is a major issue as it is a growing browser, on a growing platform.

Here is a great video of it in action: http://www.screencast.com/t/cUYKSegW0N

This issue has been repeatedly reported on the forum:

http://wordpress.org/support/topic/disappearing-images
http://wordpress.org/support/topic/multisite-images-broken
http://wordpress.org/support/topic/image-not-show-in-google-chrome-timthumbphp

Please fix this asap!"	ctsttom
Needs Dev / Bug Wrangler Feedback	18117	get_blog_details is sensitive to path's trailing slash		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-07-14T20:20:39Z	2011-11-16T01:32:02Z	"STR:
1. Create a site, then edit it so that the domain is the main domain and the path is /sub. Note that the admin doesn't turn this into /sub/, nor give an error.
2. Go to /sub/wp-admin. You'll notice it doesn't redirect, but it just gives you the main site's wp-admin. Going to /sub also just gets interpreted as a URL for the main site.

Potential solutions:
1. Make the admin automatically turn the path of /sub into /sub/.
2. Make get_blog_details match modulo trailing slash.
3. (Document carefully in Codex and hope people read it.)"	mitchoyoshitaka
Needs Dev / Bug Wrangler Feedback	21352	wp_lostpassword_url() on multisite		Multisite	3.3	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-07-23T15:58:23Z	2013-04-24T18:59:15Z	"The wp_lostpassword_url() function on Multisite outputs the link to the primary domain not the current domain.

Although it works its not what should be expected if a user is registered to use blog ID 2 but not Blog ID 1.

The lost password email generated also links back to the primary domain not the current domain.
"	philly max
Needs Dev / Bug Wrangler Feedback	20107	Add Filter for user_name length in ms user signup		Multisite		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-02-23T17:46:45Z	2012-02-23T22:44:26Z	It is difficult for us to explain our clients why they cannot have usernames with 3 chars and left. For that issue I'd like to recommend a filter for that, so we can change this with a plugin.	hughwillfayle
Needs Dev / Bug Wrangler Feedback	22917	Allow Live Updating of User & Site number in Multisite network dashboard 'Right Now' meta box		Multisite	3.5	normal	normal	Future Release	enhancement	new	dev-feedback	2012-12-13T14:54:48Z	2013-05-14T12:40:17Z	"Wordpress installation don’t show the correct number of users and sites correctly registered in the site.

Please see images for reference:

- https://dl.dropbox.com/u/7531173/mu/Only1Site1User.png
- https://dl.dropbox.com/u/7531173/mu/UsersNumber.png
- https://dl.dropbox.com/u/7531173/mu/UsersSites%20.png"	vmaia
Needs Dev / Bug Wrangler Feedback	15706	Allow wildcarded domains in multisite limited email domains	westi	Multisite		normal	normal	Future Release	enhancement	reviewing	dev-feedback	2010-12-06T18:59:24Z	2012-08-29T16:45:39Z	"Here at blogs.law.harvard.edu, we want to allow all harvard.edu subdomains to create blogs in our multisite install. There are hundreds of domains and it would be difficult to get a complete list because of the complexity of our DNS infrastructure.

I propose allowing the inclusion of a single prefix wildcard character in the limited email domains feature. If a limited email domain contains a ""*"", we would create a regex and match that specific entry via a wildcard. So ""*.harvard.edu"" would match ""cyber.law.harvard.edu"", ""fas.harvard.edu"", etc. To match the root TLD, you'd just manually enter ""harvard.edu"".

We have a variant of this applied as a core hack to our wordpress install at http://blogs.law.harvard.edu and it's been working fine for years. I will package it up as a patch if there's interest. Thoughts?

I don't think it'd make sense to allow embedded wildcards (dom*ain.org)."	djcp
Needs Dev / Bug Wrangler Feedback	20176	Allowing the Developer Filter the Regex on wpmu_validate_user_signup()		Multisite	3.4	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-03-04T23:03:53Z	2012-09-28T04:16:15Z	"So I've been having a problem with the way WordPress Multisite handles the restriction for new users. 

Looking at the file ''ms-functions.php'', I saw no Filter to the regular expression applied on the user_name to do it's validation. 

I've changed like this, so by default you will be restricted to the ''[a-z0-9]'' pattern, but if needed the developer should have the power to filter that. 

This might need a patch for the domains."	webord
Needs Dev / Bug Wrangler Feedback	20651	Inconsistent MS API: delete_site_option action hook is only called AFTER deletion, unlike delete_option		Multisite	3.3.2	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-05-10T09:54:37Z	2012-05-11T16:30:39Z	"Unlike the delete_option action hook, the delete_site_option action hook is only called AFTER deletion of the row from the sitemeta table - making it difficult to capture the expiring value (for instance), unless you know its precise option key name ( and hook it using pre_delete_site_option_{$option} ).

Suggest introducing a pre-deletion, non-specific action hook call named ""pre_delete_option"" for options and ""pre_delete_site_option"" for site options, for consistency."	danielnashnz
Needs Dev / Bug Wrangler Feedback	21156	Move utility functions out of wp-admin/network.php		Multisite		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-07-04T17:15:03Z	2012-07-04T17:15:03Z	"There are several functions in wp-admin/network.php that would come in handy outside the WP Admin -> Network Setup screen:

* network_domain_check() 
* allow_subdirectory_install()
* get_clean_basedomain()

etc.

They could be moved to wp-admin/includes/ms.php"	scribu
Needs Dev / Bug Wrangler Feedback	20152	Multisite simplify option name to user_roles		Multisite	3.3.1	normal	normal	Future Release	enhancement	new	dev-feedback	2012-03-01T21:44:28Z	2013-03-07T07:02:02Z	"Currently each blog in a MS install of WP stores an array of user roles in it's [prefix]_[$blog_id]_options table as an entry with the key [prefix]_[$blog_id]_user_roles

This makes it much harder to migrate MS install of WP to a different db prefix, etc. because not only do you need to change the table prefixes you need to go into each blog's options table and then properly update that option's key.

Because the table itself is sufficiently unique there isn't a need for this. The user roles array could be stored in an option called ""user_roles"" for each blog."	colind
Needs Dev / Bug Wrangler Feedback	14125	Seperate out non-editable options in edit site	sorich87*	Multisite		normal	normal	Future Release	enhancement	accepted	dev-feedback	2010-06-28T04:11:36Z	2010-11-30T21:52:09Z	"In the edit site screen, blog options which are arrays are shown as SERIALIZED and the textbox is disabled. The attached patch pulls those options out of the options metabox and displays the option name in another metabox below.

Related: #14120"	wpmuguru
Needs Dev / Bug Wrangler Feedback	21584	Allow to create more networks		Multisite	3.4.1	normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-08-15T00:34:24Z	2013-01-17T23:38:47Z	"After creating a multisite installation allow users to create their own network of blogs.

"	alexvorn2
Needs Docs or Unit Tests	16282	PHP catchable error with get_term_link and WP3.1RC2		Multisite	3.1	normal	major	Future Release	defect (bug)	reopened	needs-unit-tests	2011-01-18T12:23:37Z	2011-03-08T23:10:45Z	"I recently updated my WP Network to 3.1RC2, and suddenly the get_term_link() I was using in the footer gave me this error:

  PHP Catchable fatal error: Object of class WP_Error could not be converted to string

It was working fine in 3.0.4"	illutic
Has Patch / Needs Testing	21306	"Archived blogs should return HTTP ""404 Not Found"", not ""410 Gone"""		Multisite		normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-07-18T19:39:51Z	2012-07-18T19:39:51Z	"In a multisite network, if a site is archived, ms_site_check() currently serves up a HTTP 410 status code. Here's what the [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html HTTP spec] has to say about 410:

  The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.

It's acceptable to serve a 410 if the site is marked as deleted or spam, but I don't think that archiving the site is an indication that the site is permanently and irrevocably gone. Although a case can be made for changing it to 404, my contention is that a 403 is more appropriate for semantics and for bots. From the same HTTP spec:

  403 Forbidden: The server understood the request, but is refusing to fulfill it.

vs

  404 Not Found: The server has not found anything matching the Request-URI."	amattie
Has Patch / Needs Testing	16328	Auto redirect to home when www is in the URL in MU		Multisite	3.0.4	normal	major	Awaiting Review	defect (bug)	new	close	2011-01-21T04:46:08Z	2012-11-02T22:28:36Z	"I have come across a problem on my MU installation where my primary blog will automatically redirect to the home page when www is in the URL and a virtual subfolder is being called. 

Ex. http://www.domain.com/virtual_subfolder/ would redirect to http://domain.com/. 

This problem does not effect the domains that I added on with MU, only the primary site is effected. "	lelandmcfarland
Has Patch / Needs Testing	20983	Change phrasing for 'Network Activate' newly installed plugins		Multisite	3.0	normal	minor	Awaiting Review	defect (bug)	new	has-patch	2012-06-15T21:25:05Z	2012-06-16T02:28:39Z	"Not everyone is clear what 'Network Activate' means and after installing a plugin, a lot of people just assume that activate will turn it on for one site only. Then they complain that the plugin turned it self on automagically!

While it would make the link longer, I think changing it to the same wording we have in the title might actually catch their eye: ''Activate this plugin for all sites in this network''

(The other thought was to put 'Return to Plugins Page' in front of Network install, but that would annoy single site people, of whom there are a majority)"	Ipstenu
Has Patch / Needs Testing	18186	Default registration assumptions in WP Multisite		Multisite	3.2.1	normal	normal	3.6	defect (bug)	new	has-patch	2011-07-20T18:43:06Z	2012-12-29T16:25:07Z	"By default, when you create a new site, it does not set the ""registration"" site meta key.  However, in wp-signup.php by default it assumes it to ""all"" and allows users and sites to be created (line 381): 

{{{
// Main
$active_signup = get_site_option( 'registration' );
if ( !$active_signup )
        $active_signup = 'all';
}}}

However, in the network settings page, by default it sets it to none (line 75):

{{{
if ( !get_site_option( 'registration' ) )
        update_site_option( 'registration', 'none' );
}}}

With the new simple flow from a standalone to multi-site installation, new blogs should likely have it set to none by default or it should be an option during set up.

Props to leenewton for discovery."	terryjsmith
Has Patch / Needs Testing	15855	Dropdown isn't shown when doing a user 'removal'		Multisite		normal	normal	Future Release	defect (bug)	new	has-patch	2010-12-16T23:38:12Z	2012-04-27T18:14:51Z	"Steps to reproduce:

0. Have a MultiSite install
1. Go to wp-admin/users.php and delete a user
2. A confirmation screen appears, with only a ""Confirm"" button.

Expected behaviour:

The user dropdown is shown, asking to assing the user's posts to a different user.

Currently, you end up with authorless posts."	scribu
Has Patch / Needs Testing	22160	Etags served by ms-files.php not specific enough		Multisite	3.3.2	normal	normal	3.6	defect (bug)	new	has-patch	2012-10-10T23:15:01Z	2012-12-29T22:23:12Z	"Today I was tracking an Etag issue we had where different versions of images uploaded to wordpress had the same etags. I first looked at apache and reconfigured it to serve filesize mtime etags. To no avail.
When investigating further i discovered that uploaded files get an etag from ms-files.php (line 57)

{{{
$etag = '""' . md5( $last_modified ) . '""';
}}}

which to my humble opinion should be something like:

{{{
$etag = '""' . md5( $last_modified . filesize($file)) . '""';
}}}

that way, images of different formats, created at upload time, which share the same mtime on a fast machine still get different etags."	xiffy
Has Patch / Needs Testing	23555	Fatal error when sunrise added		Multisite	3.5.1	low	normal	3.5.2	defect (bug)	new	has-patch	2013-02-20T09:18:07Z	2013-03-18T13:46:48Z	"Hi,

I have installed a WordPress multisite subdomains on a server. I have added a sunrise.php file on the wp-content folder.

In this file there is a $wpdb->prepare without the needed argument at the end. WordPress throw a _doing_it_wrong() but this launch a Fatal error : 

{{{
Fatal error: Call to undefined function __() in /home/site/public_html/wp-includes/functions.php
}}}


{{{

Call Stack:
    0.0001     335660   1. {main}() /home/site/public_html/wp-admin/network/settings.php:0
    0.0001     335964   2. require_once('/home/site/public_html/wp-admin/network/admin.php') /home/site/public_html/wp-admin/network/settings.php:11
    0.0001     336260   3. require_once('/home/site/public_html/wp-admin/admin.php') /home/site/public_html/wp-admin/network/admin.php:13
    0.0002     336564   4. require_once('/home/site/public_html/wp-load.php') /home/site/public_html/wp-admin/admin.php:30
    0.0002     337136   5. require_once('/home/site/public_html/wp-config.php') /home/site/public_html/wp-load.php:29
    0.0002     337500   6. require('/home/site/public_html/wp-config-dev.php') /home/site/public_html/wp-config.php:6
    0.0003     339004   7. require_once('/home/site/public_html/wp-settings.php') /home/site/public_html/wp-config-dev.php:109
    0.0037     791980   8. require('/home/site/public_html/wp-includes/ms-settings.php') /home/site/public_html/wp-settings.php:87
    0.0038     793784   9. include_once('/home/site/public_html/wp-content/sunrise.php') /home/site/public_html/wp-includes/ms-settings.php:18
    0.0039     795552  10. wpdb->prepare() /home/site/public_html/wp-content/sunrise.php:41
    0.0039     795872  11. _doing_it_wrong() /home/site/public_html/wp-includes/wp-db.php:995
}}}

Is this normal that the translations function are not available ?"	Rahe
Has Patch / Needs Testing	20774	Flag an user as spam with any rol become a sub site flagged as spam (Multisite)		Multisite	3.0	normal	major	Future Release	defect (bug)	new	has-patch	2012-05-29T12:25:52Z	2012-11-08T21:02:31Z	"Hi,

Since many weeks, many WangGuard users were contacting me because they say WangGuard were flagging the sub sites as spam.

Thats not a WangGuard bug, is a WordPress issue.

Steps:

- Create a Subsite, you can add the Super Admin like site admin.
- Add a user like subscriber.
- Flag that user as spam in /network/users.php

That site will be flagged as spam although the owner were the Super Admin.

I think WordPress has to look for the user rol and only flag the sub site as spam if the rol is Administrator.



This issue is in WP 3.3.1 and 3.4"	j.conti
Has Patch / Needs Testing	14867	HTTPS related issues in ms-blogs.php (with fix)		Multisite		normal	normal	Future Release	defect (bug)	reopened	has-patch	2010-09-14T15:09:14Z	2011-10-13T19:18:53Z	"Two functions in ms-blogs.php have issues due to hard-coding ""http://"" versus using the is_ssl() check. I have corrected them below. Just copy and paste these over the ones in your ms-blogs.php.


function get_blogaddress_by_id( $blog_id ) {
        $protocol = is_ssl() ? 'https://' : 'http://';

        $bloginfo = get_blog_details( (int) $blog_id, false ); // only get bare details!
        return esc_url( $protocol . $bloginfo->domain . $bloginfo->path );
}

function get_blogaddress_by_domain( $domain, $path ){

        $protocol = is_ssl() ? 'https://' : 'http://';

        if ( is_subdomain_install() ) {
                $url = $protocol.$domain.$path;
        } else {
                if ( $domain != $_SERVER['HTTP_HOST'] ) {
                        $blogname = substr( $domain, 0, strpos( $domain, '.' ) );

                        $url = $protocol . substr( $domain, strpos( $domain, '.' ) + 1 ) . $path;

                        // we're not installing the main blog
                        if ( $blogname != 'www.' )
                                $url .= $blogname . '/';
                } else { // main blog
                        $url = $protocol . $domain . $path;
                }
        }
        return esc_url( $url );
}"	mareck
Has Patch / Needs Testing	20204	Incorrect links to SSL sites in Multisite		Multisite	3.0	low	normal	Future Release	defect (bug)	new	has-patch	2012-03-08T16:05:19Z	2012-11-08T00:00:19Z	"If I create a site in Multisite that has an SSL URL then a few links in Network Admin incorrectly use a non-SSL URL for the site.

Opening this ticket so I don't forget about it. Patch coming up when I have some time."	johnbillion
Has Patch / Needs Testing	14913	MS Requires Client Information to Load Files	filosofo	Multisite	3.1	normal	normal	3.6	defect (bug)	new	has-patch	2010-09-20T20:55:36Z	2013-01-10T05:42:36Z	"When installed as multi-site, WP in `ms-settings.php` tries to parse the Host header request to determine which domain is requested.  If none, it prints a redirecting Location header and exits.

This is problematic if you are loading WP but not using a client that sends headers to the server; for example, if you have another app on the same server that tries to include `wp-load.php` directly.

Example:

{{{
<?php

include '/path/to/wp/wp-load.php';

// let's do some stuff with WP programatically...
}}}

The above aborts in MS as it tries to redirect the nonexistent requesting client to the main blog's front page.

The problems I see with this:
 * `wp-load.php` is supposed to provide a means of circumventing the template printing, so it shouldn't assume a typical browser client is making the request
 * `wp-load.php` ''can'' be used this way on non-MS setups
 * In general, it's a bad jumble of MVC.

Currently I'm not sure what the best route is to fix this, but I will try to come back later with a solution."	filosofo
Has Patch / Needs Testing	19375	Make BLOG_ID folder deleted on site-deletion		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2011-11-28T00:41:57Z	2012-02-07T00:00:09Z	"It would be appreciated that the BLOG_ID folder get deleted on site-deletion, in the future..

My reference is the discussion at, 

http://wordpress.org/support/topic/wpmu_delete_blog-not-deleting-blogsdir-folder"	momotombopuro
Has Patch / Needs Testing	17376	Multisite Subfolders and bunk /wp-admin areas		Multisite		normal	normal	Future Release	defect (bug)	new	has-patch	2011-05-11T15:07:38Z	2012-04-19T01:37:52Z	"On a multisite installation with subfolders, navigating to:

www.mysite.com/i-dont-exist/wp-admin

loads a dashboard and maintains the i-dont-exist in the url.  That part exists if i navigate to themes and/or plugin pages.  However, I'm actually altering the base site.
This can be quite confusing if someone makes a typo in a sitename and they end up changing the base site (like happened to us) :("	MadtownLems
Has Patch / Needs Testing	17905	Multisite doesn't delete a user's posts/links upon removal		Multisite	3.0	normal	normal	Future Release	defect (bug)	new	has-patch	2011-06-27T12:59:43Z	2011-06-27T17:06:44Z	"When the ""Delete all posts and links."" radio is selected all that happens is the user is deleted but their posts are left in tact but without a visible user. The posts should be moved to trash as well.

This is caused by removal from the blog in `network/edit.php` before the user is actually deleted where trashing of posts occurs. Since the user no longer has any assigned blogs wpmu_delete_user() doesn't call wp_delete_post().

Patch attached also cleans up confirm_delete_users slightly by using the array passed as an argument instead of $_POST['allusers'].

Related: [13918]"	duck_
Has Patch / Needs Testing	18934	Multisite issue cleaning up empty capabilities	PeteMall*	Multisite	3.0	normal	normal	Future Release	defect (bug)	accepted	has-patch	2011-10-13T20:02:12Z	2012-11-07T22:18:09Z	"The following multisite-specific block of code in user-edit.php doesn't seem right:
{{{
		$cap = $wpdb->get_var( ""SELECT meta_value FROM {$wpdb->usermeta} WHERE user_id = '{$user_id}' AND meta_key = '{$blog_prefix}capabilities' AND meta_value = 'a:0:{}'"" );
		if ( !is_network_admin() && null == $cap && $_POST[ 'role' ] == '' ) {
			$_POST[ 'role' ] = 'contributor';
			$delete_role = true;
		}
}}}

The query appears to be checking whether the user in question specifically has no capabilities for the given blog. However, on the next line, it checks whether the result set from that query is null - that is, if the user does '''not''' have a no-capability entry. This includes users who don't have any capability entries at all (so there wouldn't be anything to delete) and users who actually have valid capabilities (whom I wouldn't think should be deleted).

It's possible I'm misunderstanding this code, but my expectations here are that the line should read {{{null !== $cap}}}.

I'm not sure if this occurs in standard workflows, but I ran into it when writing a plugin. To work around it, I back-populated {{{$_POST[ 'role' ]}}} with the user's current role."	jammitch
Has Patch / Needs Testing	20846	Multisite: Network Users can post comments without being members of the site		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-06-05T14:35:41Z	2012-11-02T23:02:52Z	"This is probably an 'ever since inception' issue and I can replicate it on 3.4

Setup:

Have a user added to your network but '''not''' to a site (domain.com/test).

Set up domain.com/test to only allow registered users to comment. Remember, we've not added this new user to the site, just the network.

Log in as that user and go to domain.com/test

Oh look! You can comment as a 'registered' user.

This should be check for 'Is this a user ''and'', if multisite, is this user a member of the site?'

It's that or the wording needs to be clearer that anyone registered on the network can comment."	Ipstenu
Has Patch / Needs Testing	21573	NOBLOGREDIRECT interfering with 404 errors		Multisite	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-08-14T07:32:06Z	2013-04-16T05:36:08Z	When the `NOBLOGREDIRECT` constant is defined, 404 pages on the main site will not work and instead redirect to URL defined in `NOBLOGREDIRECT`. This is the cause of the `maybe_redirect_404` action/function, which is not needed and should be removed.	bungeshea
Has Patch / Needs Testing	16568	Network install disables site when blog_id is not 1		Multisite	3.0.5	normal	normal	Future Release	defect (bug)	new	has-patch	2011-02-15T20:07:03Z	2011-02-16T01:31:33Z	"This is an edge case and only occurs when MySQL is configured to skip numbers in auto number fields.

The network install inserts the blog record and allows MySQL to assign the blog_id. The blog prefix logic in wpdb depends on the blog_id of the main blog being 1.

The manual fix for this is to edit the DB and change the blog_id of the main blog to 1. Between being an edge case and a relatively easy fix, this isn't severe, imo.

Forum thread: http://wordpress.org/support/topic/database-error-when-enabling-mutlisite"	wpmuguru
Has Patch / Needs Testing	15956	Remove user link should be red		Multisite		normal	normal	Future Release	defect (bug)	new	has-patch	2010-12-22T23:10:02Z	2012-05-01T14:07:04Z	"On MultiSite, a user has a 'Delete' action link, which erases them from the system completely. It is red.

When going to `Network Admin -> Sites -> Edit Site -> Users` there is a 'Remove' link, which only erases a user from a certain site in the network. This is currently blue.

Since it's still a destructive action (no trash), the 'Remove' link should be red as well."	scribu
Has Patch / Needs Testing	19724	Sites with IDN domains can't be created (bug #15554 continuation)		Multisite	3.3	normal	normal	Future Release	defect (bug)	new	has-patch	2012-01-03T17:44:08Z	2012-04-17T04:02:31Z	"registration of new site with idn domain by unknown/new users themselves is not possible.
(though creation of new site in wp-admin/network/site-new.php page is possible, by patch given in bug #15554 , i have just now tested it.)

also let i mention that site domain is written (and would be requested to enter, if would be fixed without punycode to unicode conversion) in punicode form in wp-signup.php page, that is not acceptable for wordpress.

i have attached differences i made to wp 3.0.4 to make idn domains working and also to show and accept them in human readable format in wp-signup.php page . link to the differences file i attached to/in previous bug report on/to this topic: http://core.trac.wordpress.org/attachment/ticket/15554/diff304-blogo.txt ."	qdinar
Has Patch / Needs Testing	20825	User activation in multisite should happen in the main blog..		Multisite		normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-06-04T11:00:41Z	2012-11-02T22:52:08Z	"In multisite mode ( subdomain ) , when a user activates his account, it should happen in the main blog ( or not ? ) .

In ms-settings.php ( line 118 ) , we assume that the main blog is always blog=1 ( which may be wrong ) . 

The attached patch uses the constant BLOG_ID_CURRENT_SITE if defined instead."	rahal.aboulfeth
Has Patch / Needs Testing	20116	Welcome User Email in Multisite Can't Be Changed		Multisite	3.3	normal	normal	Future Release	defect (bug)	new	has-patch	2012-02-24T21:44:28Z	2012-05-02T20:32:08Z	"Reproduced this on 3.3 and 3.4-aortic.

Go to /wp-admin/network/settings.php

Add 'New' to the sentance 'Welcome User' to make it 'Welcome New User'

Hit update.

Page refreshes, text does not change."	Ipstenu
Has Patch / Needs Testing	23418	banned names / illegal_names not being banned		Multisite	3.5.1	normal	normal	3.5.2	defect (bug)	new	has-patch	2013-02-08T04:41:52Z	2013-05-10T16:59:56Z	"new site registrations are ignoring the banned names i add to the list in network options.

out of the gate the default banned names function works and the system does not let me register any of those default names. the illegal_names value in the wp_sitemeta table is populated with: '''''a:7:{i:0;s:3:""www"";i:1;s:3:""web"";i:2;s:4:""root"";i:3;s:5:""admin"";i:4;s:4:""main"";i:5;s:6:""invite"";i:6;s:13:""administrator"";}'''''

when i add '''''seven eight nine''''' to the banned names field of the network setting page and save the page, the banned names field is populated with '''''www web root admin main invite administrator seven eight nine''''', just how you would expect. but now the illegal_names value in the db is '''''a:1:{i:0;s:61:""www web root admin main invite administrator seven eight nine"";}'''''

notice how the serialized array only has one string now instead of the original multiple strings. once it is saved like this users can register any site name including defaults like admin and root plus the new names i added to the list.

my setup: two fresh multisite 3.5.1 installs. one is on a vps and the other on a local xampp install. no plugins activated nor installed. using twenty twelve theme. these are test installs."	dohman
Has Patch / Needs Testing	20589	domain_exists should add trailing slash to path		Multisite	3.0	normal	minor	Awaiting Review	defect (bug)	new	has-patch	2012-05-01T16:49:18Z	2012-07-03T00:36:37Z	{{{insert_blog}}} runs {{{trailingslashit}}} on the path, however, {{{domain_exists}}} uses whatever is passed in. If WP is enforcing the trailing slash on blog insertion, it really should when checking existence. It should probably also cast the site_id as an int per {{{insert_blog}}}.	ejdanderson
Has Patch / Needs Testing	14730	ms-files.php required ob_clean() and flush()	westi*	Multisite		normal	normal	Future Release	defect (bug)	accepted	has-patch	2010-08-30T04:53:20Z	2013-02-05T16:17:29Z	"I recently migrated a development wp 3 multisite install to 'live' mode for a site launch.  One problem I had is that images served out of /files stopped working.  Everything looked fine as far as the response / headers, but the image would open up as corrupted.  

After quite a bit of troubleshooting, the problem went away when I added ob_clean() and flush() calls to ms-files.php just before the readfile($file) call at the end of the file.  Perhaps this is due to a problem elsewhere in my site, but I'm creating this bug so someone can decide if adding the buffer flush would be a reasonable addition to the codebase.  It seems like this is the recommended way of doing things according to the sample code here:

http://us2.php.net/manual/en/function.readfile.php"	pj_mfc
Has Patch / Needs Testing	17168	redirect loop when accessing wp-admin/network/		Multisite	3.1.1	normal	normal	Awaiting Review	defect (bug)	reopened	has-patch	2011-04-18T17:59:55Z	2012-08-10T06:31:44Z	"As of 3.1.1 administrators are getting redirect loops when accessing wp-admin/network/. I run a multi-site multi-domain network and we've noticed that this bug is effecting new and old sites. One super admin reported clicking Update Network put's it in a redirect loop as well.

For new sites if this bug occurs the quick solution is to delete / recreate. I checked _options siteurl, _blogs blog_id domain, and _sitemeta siteurl. Nothing out of the ordinary in the db."	chaos1
Has Patch / Needs Testing	23637	wp-signup.php has overly aggressive CSS		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2013-02-27T14:33:46Z	2013-02-27T18:25:15Z	The CSS added through wp_head by wp-signup.php stops Multisite form fields from being styled through inheritance. Allowing inheritance will result in more consistent styling with the active theme (for example, field font-size).	kwight
Has Patch / Needs Testing	21662	wp-signup.php says there's no limit to the number of blogs even when that is not desired or impossible		Multisite	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-08-22T20:48:26Z	2012-12-29T16:53:04Z	"Please remove the statement in '''wp-signup.php''' that exclaims that there's no limit to the number of blogs one can create. It's on line 169.

I ask for two reasons:
1. Hosters of WordPress Networks may not wish to encourage users to open a ton of blogs. I don't because I don't want to encourage a support nightmare.
2. We might use a plugin that limits the number of blogs that users may create, like [http://buddydev.com/buddypress/limit-blogs-per-user-plugin-for-wpmu/ Limit Blogs per User].

For #2, an acceptable alternative may be to make it a string that can be overridden by a plugin. But the current situation, where it's a one-size-fits-all string, is bad because I have to manually edit it each time I (frequently) upgrade WordPress."	novasource
Has Patch / Needs Testing	21143	Add a hook for when no blog is found (in addition to NOBLOGREDIRECT)		Multisite		normal	normal	Future Release	enhancement	new	has-patch	2012-07-03T01:20:45Z	2012-11-07T22:18:40Z	"(Related to #21142)

'''Background'''

On a multisite install, we allow users to change their subdomain name (or domain name).

We keep a list of their previously used subdomains/domains, and if there is a HTTP request for one of their old domains, we automatically perform a 301 redirect to the new domain name.

'''Problem'''

In order to perform a 301 redirect from and old domain to the new domain, we currently have to use wp-content/sunrise.php.

However we would like to take advantage of the logic at the top of wp-includes/ms-settings.php, rather than re-inventing that logic in our sunrise.php file.

The NOBLOGREDIRECT constant can be used for this, but it does not allow us to perform a 301 redirect.

'''Solution'''

Adding a simple hook to ms-settings.php would allow a sunrise.php file to determine what should happen if a HTTP request on a Multisite install does not correspond to one of the existing sites/blogs.
See attached patch."	jamescollins
Has Patch / Needs Testing	15828	Alphabetized My Sites	jakub.tyrcha*	Multisite		normal	minor	Future Release	enhancement	accepted	has-patch	2010-12-15T15:52:48Z	2013-02-08T13:42:00Z	"For installs that have lots of sites it would be easier to browse if the sites are alphabetized. I add the following code to our install after each update. It would be nice if this was the default. 

after line 72: reset( $blogs );
{{{
	function cmp($a, $b){
		if ($a->blogname == $b->blogname)return 0;
		else return ($a->blogname < $b->blogname) ? -1 : 1;
	}
	uasort($blogs, 'cmp');

}}}"	scep
Has Patch / Needs Testing	19451	Cannot distinguish which WordPress Signup stage I am		Multisite	3.3	normal	minor	Awaiting Review	enhancement	new	has-patch	2011-12-05T23:35:02Z	2011-12-06T20:30:15Z	"As a plug-in developer under WordPress MS I would like to recognize at which stage I am of the signup:
1. first page because of some errors
2. blog confirmation page in case of no errors

Unluckily as today we have:
<input type=""hidden"" name=""stage"" value=""validate-blog-signup"" />

that is the same for the whole process instead would be nice to have a different value there.

Plus we have:
<?php do_action( 'signup_hidden_fields' ); ?>

But even this action is called in both stages.

So how about start naming the stages differently and also call different actions?
For example I want to include some hidden fields only when I am sure all errors are gone and I am already on confirmation of blog name stage.
I don't see this possible right now."	Cimmo
Has Patch / Needs Testing	22383	Combine Domain and Path UI		Multisite		normal	normal	Future Release	enhancement	new	has-patch	2012-11-07T22:30:08Z	2012-11-08T01:03:40Z	"When editing a site in /network/site-info.php?id=123 you get two fields: one for the site's domain and another for the path.

It would make more sense from a UX perspective to have a single URL field, which would be intelligently parsed on save."	scribu
Has Patch / Needs Testing	24061	Introduce blog-archived.php and blog-spam.php		Multisite		normal	normal	Awaiting Review	enhancement	new	has-patch	2013-04-12T16:54:46Z	2013-04-13T08:54:29Z	"When Multisite is active and an archived or spammed site is loaded, WordPress first looks for a file in the content directory called `blog-suspended.php` and loads it if it's found.

Two problems:

 1. The file name is counter-intuitive because 'suspended' isn't the name of a status that a site can have.
 2. It's not possible to serve a different file for spammed and archived sites.

The upcoming patch introduces support for `blog-spam.php` and `blog-archived.php` for sites with the respective status. It will fall back to `blog-suspended.php` for backwards compatibility."	johnbillion
Has Patch / Needs Testing	19753	Network admin pages don't show network name in page title		Multisite	3.0	normal	trivial	Future Release	enhancement	new	has-patch	2012-01-05T22:24:18Z	2012-04-27T18:47:27Z	When you're on network admin screens, the page `<title>` doesn't contain the network name, unlike site admin screens which contain the site name.	johnbillion
Has Patch / Needs Testing	19996	New function get_blog_metadata for ms-functions.php		Multisite		normal	minor	Awaiting Review	enhancement	new	has-patch	2012-02-09T10:20:20Z	2012-02-09T10:20:20Z	"Hi!

I think that the ms-functions are very useful for WP multisite developers, for example: get_blog_post where you can select the blog_id and post_id to return the post info of a blog.

But I'm missing an important one: get_blog_post_metadata. With the function that I'm proposing, you can select the blog_id, the post_id and the meta_key and the function will return the metadata for those values.

I have attached in the file get_blog_metadata.txt the function that I have made and I think it would be very useful to have it in the core.

Cheers! :)"	_DorsVenabili
Has Patch / Needs Testing	18292	Not interrupting the network update, even if errors are detected		Multisite	3.2.1	normal	normal	Future Release	enhancement	new	has-patch	2011-07-29T10:24:41Z	2012-04-18T21:00:28Z	"'''My installation'''[[BR]]
3.2.1 multi-site installation with almost 8000 sites.

'''The issue'''[[BR]]
During the network update, I kept getting this error message :[[BR]]
''Warning! Problem updating http://username.example.com. Your server may not be able to connect to sites running on it. Error message: 0: Empty reply from server.''[[BR]]
The problem is that the network update script (/wp-admin/network/upgrade.php) dies every time an error is detected, so I had to reload the page every time. With nearly 8000 sites to update, it was impossible, so I modified that script.

'''Suggested enhancement'''[[BR]]
Enhance the network update script so that it doesn't die at each error, logs the error and continues. A second run on the unsuccessful upgrades would also be nice."	luuzan@…
Has Patch / Needs Testing	17630	Redirect wp-signup.php to wp_signup_location		Multisite	3.1.3	normal	minor	Awaiting Review	enhancement	new	has-patch	2011-05-31T23:03:15Z	2012-11-17T15:43:47Z	"I noticed that if wp-signup.php is accessed directly and wp_signup_location is not the default ""site_url( 'wp-signup.php' )"", it does not redirect to the signup location.

I've attached a potential patch. It works for me."	dwieeb
Has Patch / Needs Testing	23709	Relax wildcard restrictions for populate_network() when installing in subdomain mode		Multisite	3.5	normal	normal	Awaiting Review	enhancement	new	has-patch	2013-03-06T20:03:49Z	2013-04-01T09:25:14Z	"I ran into the issue while trying to use wp-cli install-network command with --subdomains support.

Underlying core issue is that populate_network is trying to check if wildcard subdomain is accessible. This makes sense for large networks, but might not work with certain setups, or not needed for small sites.

Proposed solution is to add extra arg for populate_network() $wildcard_check with default to true. See attached patch"	rinatkhaziev
Has Patch / Needs Testing	21546	Site Settings page is a hot mess		Multisite	3.0	normal	normal	Awaiting Review	enhancement	new	has-patch	2012-08-10T21:44:07Z	2012-08-20T16:50:59Z	"I found out just how bad this page is when debugging an issue related to {{{WPLANG}}}. {{{WPLANG}}} is an option for a blog in your network (overrides {{{WPLANG}}} in {{{wp-config.php}}}), but if you delete the option on purpose or accidentally, there is no way of restoring it in the admin.

Site Settings just loads your options table and POSTs back to itself. The only reference to the original options map (the defaults) is in schema, which WP has zero access to outside of upgrade.

I have abstracted the default options and the default ""fat"" options into functions in {{{ms.php}}}. Also, when loading your Site Settings options - if a default option is missing, I display it in the admin so you can save it (it is populated with its default value).

I have also streamlined and condensed some code that was happening in and around {{{populate_options()}}}"	wonderboymusic
Has Patch / Needs Testing	18910	get_blog_details query alteration for root-relative url plugin support...		Multisite	3.2.1	normal	normal	Awaiting Review	enhancement	new	has-patch	2011-10-11T23:39:05Z	2011-10-28T22:28:13Z	"After reading through this ticket http://core.trac.wordpress.org/ticket/17048 and all of its referenced links / discussions I decided to write my own plugin to do root-relative urls.

However there is a core issue that prevents such a plugin from working when using path-based MU installs (versus subdomain installations where as it stands cannot support root relative urls... yet.)

Looks like the logic for path-based site detection was copied wholesale from the subdomain-based detection logic in the if-block just below it.  

I don't see a need to query both the path and the domain if the domain isn't going to change for a MU path-based install.  This fix proposes checking explicitly for is_subdomain_install == false and then only querying the database on the path column.  

If this patch doesn't account for some scenario in which path-based installs could actually have multiple domain addresses in the database then please add a filter to the $fields variable so that a plugin can handle the variance there.

I'm not here to start a root-relative vs absolute uri debate (I'm saving that for another day ;)  But basically the recommendation from the WP Core team is to do this in a plugin, yet we can't until this is fixed.

Thanks!
-Marcus

(ps - if you'd like to have the absolute uri / relative root debate I'm totally game! just email me :D)"	MarcusPope
Has Patch / Needs Testing	23650	make get_space_allowed() filterable		Multisite	3.4	normal	normal	Awaiting Review	enhancement	new	has-patch	2013-03-01T00:38:34Z	2013-03-01T00:57:30Z	"When the `blog_upload_space` option is set to `0`, instead of returning `0`,  `get_space_allowed()` returns the default value which is currently hardcoded to `50` in core.

As discussed in #18119 and committed in [19314], the function should return `0` if the option is set to `0`. However this was reverted in [19654] (see #19538). So I am not sure which is the desired behaviour.

The attached patch adds filters for the default value and for the returned value. This is useful for scenarios where you don't want it to fallback to `50` if the option is accidentally set to `0`, and you want to set your own default.

I can adjust the patch if the consensus is that an option of `0` should in fact return `0`."	jkudish
Has Patch / Needs Testing	14511	new function - wp_get_sites($args)		Multisite		normal	normal	Future Release	enhancement	new	has-patch	2010-08-02T22:02:54Z	2012-09-18T17:24:15Z	"With the deprication of get_blog_list (and the dire warnings), we had a need for a function to retrieve a list of blogs. At first blush, it appears that one could use get_blogs_of_user. It seems to assume that the same admin (userid 1) is going to create all sites. If you have multiple network_admins, then a search for a single user's sites won't return a full list.

So I have adapted the code from wp-admin/ms-sites.php and with a nod to wp_list_pages - am submitting wp_get_sites for a future release.

This function accepts an argument list to filter the results, modify the order, and limit the range of results. I wrote it with an eye to provide an interface consistent with other wp functions, as well as potentially replacing the sql query in wp-admin/ms-sites.php.

The initial set of arguments include:
{{{
			'include_id' 		,				// includes only these sites in the results, comma-delimited
			'exclude_id' 		,				// excludes these sites from the results, comma-delimted
			'blogname_like' 	,				// domain or path is like this value
			'ip_like'			,				// Match IP address
			'reg_date_since'	,				// sites registered since (accepts pretty much any valid date like tomorrow, today, 5/12/2009, etc.)
			'reg_date_before'	,				// sites registered before
			'include_user_id'	,				// only sites owned by these users, comma-delimited
			'exclude_user_id'	,				// don't include sites owned by these users, comma-delimited
			'include_spam'		=> false,		// Include sites marked as ""spam""
			'include_deleted'	=> false,		// Include deleted sites
			'include_archived'	=> false,		// Include archived sites
			'include_mature'	=> false,		// Included blogs marked as mature
			'public_only'		=> true,		// Include only blogs marked as public
			'sort_column'		=> 'registered',// or registered, last_updated, blogname, site_id
			'order'				=> 'asc',		// or desc
			'limit_results'		,				// return this many results
			'start'				,				// return results starting with this item
}}}
The usual warning are provided. It works for me but I haven't tested it completely yet. But I am assuming this could be helpful to others and I have no doubt about getting comments back <grin>"	transom
Has Patch / Needs Testing	20019	wpmu_validate_blog_signup(): Allow '.' and '-' in blog names		Multisite	3.3.1	normal	normal	Future Release	enhancement	new	has-patch	2012-02-10T23:04:29Z	2012-04-26T12:33:25Z	"Canonical uses Wordpress 3.x multisite as part of voices.canonical.com, for employees who do not have or wish to list their personal blog.  The code is stock, except for one patch we maintain, which allows blog names (currently in WP as lowercase alphanumeric only) to also include '.' and '-'.  This matches our global username format.

Attached is a patch extending wpmu_validate_blog_signup() to allow '.' and '-', with a tweak for the error text.  We have been running the patch for awhile, and have not run across any problems with the rest of the code accepting this."	fo0bar
Has Patch / Needs Testing	21674	"Please add ""plugins"" link under ""my sites > network admin"" in toolbar"		Multisite	3.4.1	normal	normal	Awaiting Review	feature request	new	has-patch	2012-08-23T19:13:46Z	2012-08-24T15:43:16Z	This would remove a click and I think a lot of people would enjoy the addition. I know I go to the plugins page more than users or sites combined.	archonic
Has Patch / Needs Testing	18079	WP has dropped support of the path field in the site table		Multisite	3.0	normal	normal	Awaiting Review	feature request	new	has-patch	2011-07-12T05:06:31Z	2012-11-03T14:25:50Z	"I've had inquiries about sites that used to work in WordPress Mu that no longer work in WordPress 3.1.  

The idea is to have a path based network for each state/province and sites for each city under that, all networks hosted under the same domain. 

Like so
{{{
Network 1:
Network domain: example.com Network path: /ohio/
    site domain: example.com path: /ohio/akron
    site domain: example.com path: /ohio/canton
    site domain: example.com path: /ohio/uniontown

Network 2:
Network domain: example.com Network path: /pa/
    site domain: example.com path: /pa/pittsburgh
    site domain: example.com path: /pa/greensburg
    site domain: example.com path: /pa/erie

Network 3:
Network domain: example.com Network path: /indiana/
    site domain: example.com path: /indiana/indianapolis
}}}
There are two things that are preventing this. First, in new_site, instead of including the path from the sites table for the current network, it uses the global $base variable which is always / in this scenario. Using $current_site->path resolves that. 

The second issue is that the .htaccess code is too restrictive. It will the paths on two levels. /network/site/wp-admin/ doesn't work but /site/wp-admin/ does.

Adjusting lines similar to 
{{{
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1
}}}
over to 
{{{
RewriteRule  ^[_0-9a-zA-Z/-]+/(wp-(content|admin|includes).*) $1
}}}
resolves that.

The attached patch addresses both of these requirements.
"	brianlayman
Has Patch / Needs Testing	12756	WPMU does not handle files with two or more dots in the filename	wpmuguru	Upload	2.9.2	normal	minor	Future Release	defect (bug)	reopened	has-patch	2010-03-29T07:23:50Z	2012-11-03T22:59:51Z	"* WPMU does download images that have two or more dots in the file name
> E.g., One..jpg One...jpg One....jpg

rewrites do work (checked)

* this is clearly a WP issue:
> /wp-content/blogs.php
...
$file = BLOGUPLOADDIR . str_replace( '..', '', $_GET[ 'file' ] );
if ( !is_file( $file ) ) {
	status_header( 404 );
	die('404 &#8212; File not found.');
}
...
> WPMU removes two dots!!!

> workaround:
$file = BLOGUPLOADDIR . $_GET[ 'file' ]; // name.ly: workaround for files with two or more dots

tested and works fine
"	Namely
Has Patch / Needs Testing	16235	Site Welcome Email sent without regard to noconfirmation flag		Users	3.1	normal	normal	Future Release	enhancement	new	has-patch	2011-01-14T19:18:34Z	2011-09-15T23:31:22Z	"In multisite and the super_admin adds a new user to a site, 
if the user is new to the network, WP sends out the welcome email (but not the confirmation of being added to the site)

In my client's use case, they were looking for the SBD (silent but deadly) mode, as in no email at all should go out.

The language implies there is ""no"" notification but the welcome email belies that language.

if even the welcome email should be disabled, then 
in wp-admin/user-new.php (around line 108)
adding
`add_filter('wpmu_welcome_user_notification', ''__return_false');`
would kill the new user notification from wpmu_activate_signup() (a few lines later)
"	transom
Needs Reporter Feedback / Steps To Reproduce	23453	Absolute path added to same page anchor tag links		Multisite	3.5.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-02-12T04:56:18Z	2013-02-20T03:42:34Z	"In a multisite setup with a sub-folder configuration when I create a link with a hash tag to an anchor point on the same page, the rendered HTML includes the absolute path plus the hash tag.

When I tested creating a same page link with a hash tag on a regular install it worked fine. This might have to do with re-writes using sub-folders in multisite. I don't think it should be adding the absolute path into the href"	angio
Needs Reporter Feedback / Steps To Reproduce	20746	Accessing non-existing theme folder in Network install gives 500 error		Multisite	3.3.2	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-05-25T10:28:39Z	2012-11-17T16:17:46Z	Accessing non-existing theme folder in Network install gives 500 error and following error in error log: ''Request exceeded the limit of 10 internal redirects due to probable configuration error.''	arkimedia
Needs Reporter Feedback / Steps To Reproduce	21428	Bad mail subject encoding on new blog notification		Multisite	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-07-31T14:02:59Z	2012-08-07T11:43:45Z	"Email subject is in Russian language. When trying to add new blog using page http://mysite.com/wp-admin/network/site-new.php, user gets email where subject is like - '''=??B??='''. So I was trying to find where this bug appears. And I think, I found it. 

Script tries to send notification using function '''wpmu_welcome_notification''' on line http://core.trac.wordpress.org/browser/tags/3.4.1/wp-includes/ms-functions.php#L1250. But '''get_option('blog_charset')''' returns empty string, so header is bad-generated and encoded..."	TheSteelRat
Needs Reporter Feedback / Steps To Reproduce	23728	Errors when trying to upload media before saving network settings		Multisite		normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2013-03-09T03:28:47Z	2013-03-21T16:43:14Z	"foreach warning due to unpopulated $mimes array and denial of uploads even when file types defined in network admin settings. This seems to happen because there is a disconnect between the defaults and what is actually present in the db (before the first save).

Should be noted that the site was installed programmatically using wp_install() so this may have something to do with it. I am giving this a major severity because the server path is disclosed from the foreach warning and the least that should be done is do an is_array() check on that $mime var and give a meaningful message stating that there are no mimes defined or something..."	wp4j
Needs Reporter Feedback / Steps To Reproduce	24017	Network admin sites list page displaying bad links for Dashboard and Visits		Multisite		normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-04-09T22:44:04Z	2013-04-10T06:14:46Z	"After upgrading to 3.5.1 (from 3.5), we noticed that the links to Dashboard and Visits in the/wp-admin/network/sites.php weren't working properly.

For subsites, the Dashboard link pointed back to the root site, and the same for the Visits link.

I traced the code to the following file: /wp-admin/includes/class-wp-ms-sites-list-table.php.

Line 251 currently is:


{{{
$actions['backend'] = ""<span class='backend'><a href='"" . esc_url( get_admin_url( $blog['blog_id']
     ) ) . ""' class='edit'>"" . __( 'Dashboard' ) . '</a></span>';
}}}


Adding the $blogname variable to the get_admin_url function as the second parameter fixed the issue:


{{{
$actions['backend'] = ""<span class='backend'><a href='"" . esc_url( get_admin_url( $blog['blog_id']
    , $blogname ) ) . ""' class='edit'>"" . __( 'Dashboard' ) . '</a></span>';
}}}


Similarly for the Visits link.

Line 272 currently is: 


{{{
$actions['visit']   = ""<span class='view'><a href='"" . esc_url( get_home_url( $blog['blog_id'], '/
    ' ) ) . ""' rel='permalink'>"" . __( 'Visit' ) . '</a></span>';
}}}


Changing it to the following fixes it:


{{{
$actions['visit']   = ""<span class='view'><a href='"" . esc_url( get_home_url( $blog['blog_id'], $blogn
ame ) ) . ""' rel='permalink'>"" . __( 'Visit' ) . '</a></span>';
}}}

"	morriswanchuk
Needs Reporter Feedback / Steps To Reproduce	22434	User E-Mail Change confirmation email is not being sent in multisite		Multisite	3.4.2	normal	minor	Awaiting Review	defect (bug)	new	reporter-feedback	2012-11-13T16:09:13Z	2012-11-14T00:14:41Z	"Hi there,

I noticed a slight issue for Wordpress Multisite 3.4.2.

When trying to change the super-admin e-mail address wordpress notifies that an email confirmation needs to be sent out to the e-mail address. 

That confirmation is never sent, however all other emails generated by wordpress are being sent fine. This occurs on a private server (so no shared hosting restrictions)

I am trying the email change on the main network home site (site id=1).
Password reset instructions and comment notifications are being sent successfully from the same site (id=1).

I know that the email address can be changed from within the database, but I thought I'd let you know. 

Please let me know if you require additional info about the environment or wp install. 

Thank You,

Adrian"	taropaa
Needs Reporter Feedback / Steps To Reproduce	20854	functions.php on line 155 ?	Nikolaos Raftopoulos	Multisite	3.3.2	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-06-06T12:45:29Z	2012-07-31T02:42:37Z	"In my network dashboard I get the following error message : 


Warning: number_format() expects parameter 1 to be double, string given in /home/tklighth/public_html/wp-includes/functions.php on line 155"	leondari
Needs Reporter Feedback / Steps To Reproduce	23212	wp_signup.php always get 404 status header		Multisite	3.5	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-01-16T02:04:14Z	2013-01-16T04:20:54Z	"I get 404 in status header for wp_signup.php in few server,

I think it was caused by class WP->handle_404();

"	apineraka
Needs Patch	6822	Admin colors should be per-blog	ryan	Administration	2.5	normal	normal	Future Release	enhancement	new		2008-04-23T02:07:08Z	2010-03-25T05:58:52Z	When shared user tables are used, changing the colors for one blog should not change it for all.	matt
Needs Patch	10947	Problem on import <embed> codes on mt.php script	Edgar Gabaldi	Import	2.8.4	normal	normal	WordPress.org	defect (bug)	new		2009-10-12T16:59:13Z	2012-05-24T22:33:11Z	"I'm having trouble making the import of a file exported by CMS Movable Type.

All posts, categories, comments, users are imported correctly. The problem is that there are blocks of code in posts with the tag <embed> that are not being imported."	edgabaldi
Needs Patch	15594	"make pluggable the multisite/""wpmu"" mails"		Mail	3.1	normal	minor	Future Release	enhancement	new		2010-11-27T11:45:35Z	2011-01-13T03:29:18Z	"such as the one that is generated in the first lines of

wp-admin/user-new.php"	arena
Needs Patch	22128	Adding upload mimetype in Multisite does not work if mimetype is not already defined		Multisite	3.0	normal	critical	Awaiting Review	defect (bug)	new		2012-10-08T13:13:54Z	2012-12-23T17:11:20Z	"'''Description'''

We would like to add 3gp to the list of file types to be uploaded in the sites of our network install. 

We've tried to add 3gp to the Network Settings->Upload File Types setting for this. However after having saved the setting we were still not able to upload 3gp. It seems the user setting is being overruled by the list of global settings.  

'''Steps to reproduce issue:'''
1. Use WordPress Network install (aka Multisite)
2. Add the file extension 3gp to the upload file types setting in Network Settings
3. Save Settings
4. Try to upload a 3gp file using the Media Library, it will fail with the message: 'Sorry, this file type is not permitted for security reasons.'

It seems the upload file types defined in the Network Settings cannot overrule / add new file types if this file type has not already been defined in the function wp_get_mime_types() (see file: wp-includes/functions.php). 

'''Expected behaviour'''

Changing the Upload File Types by adding a new extension results in WordPress accepting files ending in this extension. Or warn the admin that this extension is unknown and more info (such as the full mime type) is needed. 

'''Proposed solution'''

We are aware of the hook 'upload_mimes' to fix this with a plugin, but we suggest that the superadmin Network Settings->upload file type overrules WordPress' built-in defaults instead of the other way around."	BjornW
Needs Patch	18272	Can not define media upload path/URL in multisite		Multisite	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-27T22:56:44Z	2011-07-27T22:56:44Z	"We have a multisite installation with five subdomains.  We do not wish to use the default /files/yyyy/mm/filename.ext structure for uploaded media.

In Network Admin > Sites > Edit (under a subdomain) > Settings, you can set:
Upload Path (eg /var/www/pathonserver)
Upload Url Path (eg http://www.domain.com/pathonserver)
Fileupload Url (eg http://www.domain.com/pathonserver)

However WordPress does not recognise these settings and uses the default format.

If you comment out the last line on wp-includes/ms-settings.php (ie ms_upload_constants()), it does recognise the settings. "	xtraxtra
Needs Patch	20171	Categories/Tags links are broken in WP 3.3.1, with multisite/subfolder install		Multisite	3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-03-04T07:10:35Z	2012-03-04T13:21:39Z	"All the default categories/tags links are not working, showing error..

""This is somewhat embarrassing, isn’t it?""

Steps to reproduce:
-------------------
1. Install WP 3.3.1 on domain, e.g. http://blog.example.com
2. Enable multi-site features, using subfolder instead of subdomain
3. Create a site, e.g. http://blog.example.com/test1
4. Create a post, e.g. http://blog.example.com/test1/2012/03/04/test1/
5. Enter the default category link, e.g. http://blog.example.com/test1/category/uncategorized/


Now you will see the message: ""This is somewhat embarrassing, isn’t it?""

Fix:
----
1. Enter this link: http://blog.example.com/test1/wp-admin/options-permalink.php
2. Change nothing, press ""Save Changes""
3. Now you can view the link correctly: http://blog.example.com/test1/category/uncategorized/

The above issue also apply to tags"	tszming
Needs Patch	21036	DB Repair on Multisite looks for wp_1_....		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new		2012-06-21T12:37:40Z	2012-12-10T00:26:59Z	"Log in to your site and need to repair. WP nicely prompts you, so you click the repair button and get this:


{{{
wp_1_posts: Table 'wordpress.wp_1_posts' doesn't exist
wp_1_comments: Table 'wordpress.wp_1_comments' doesn't exist
wp_1_links: Table 'wordpress.wp_1_links' doesn't exist
wp_1_options: Table 'wordpress.wp_1_options' doesn't exist
wp_1_postmeta: Table 'wordpress.wp_1_postmeta' doesn't exist
wp_1_terms: Table 'wordpress.wp_1_terms' doesn't exist
wp_1_term_taxonomy: Table 'wordpress.wp_1_term_taxonomy' doesn't exist
wp_1_term_relationships: Table 'wordpress.wp_1_term_relationships' doesn't exist
wp_1_commentmeta: Table 'wordpress.wp_1_commentmeta' doesn't exist
}}}


I've seen this over and over again, and generally I tell people to go into phpMyAdmin and repair there, which works. But clearly looking for wp_1_ is going to be problematic for non-WPMU upgraded sites. Which are quickly becoming the majority."	Ipstenu
Needs Patch	17397	Inconsistency in allowed site addresses		Multisite	3.1	normal	minor	Awaiting Review	defect (bug)	reopened		2011-05-12T14:40:09Z	2012-11-02T22:34:33Z	"The rules for allowed characters in a site address differ between when you add a new site and when you edit an existing site.

Steps to reproduce:

 1. Go to Network Admin -> Sites -> Add New
 2. Enter `foo.bar` as the site address and hit save. The address will be rejected as containing invalid characters.
 3. Edit an existing site instead, and enter `foo.bar.yourdomain.com` as the domain. The address will be accepted just fine.

Having written that out, maybe this isn't a valid bug because when adding a site you're entering the site address, but when you're editing a site you're editing the complete domain name. Hmm. I'll open it anyway and see what people think.

My core issue is that I'd like to be able to add sites that use fourth-level subdomains (eg `foo.bar.baz.com` when the main site is at `baz.com`). Currently I have to enter a different site address then go in and edit it to the desired domain."	johnbillion
Needs Patch	23483	Incorrect image URL for subsites when using UPLOADS constant on multisite subdirectory installation		Multisite	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-15T18:56:54Z	2013-02-18T21:40:51Z	"If the UPLOADS constant is used on a Wordpress Multisite installed to subdirectory, using subdirectory mode, then image URLs for subsites are incorrect.

Example:
* WP MS installed to www.domain.com/wordpress, subdirectory not subdomain
* UPLOADS set to 'assets'

Main site uploads images to /wordpress/assets/... [[BR]]
Main site image URL is www.domain.com/wordpress/assets/...

1. Create subsite called 'subsite';
2. Subsite uploads images to /wordpress/assets/sites/2/...
3. Subsite image URL is www.domain.com/subsite/assets/sites/2/... when it should be www.domain.com/assets/sites/2/...


This is because wp_upload_dir() uses get_option('siteurl') to derive the URL. It is probably right for subdomain multisite but wrong in this use case."	creativeinfusion
Needs Patch	20440	Initial admin user only removable through bulk action when using multisite network		Multisite	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-04-14T02:51:59Z	2012-04-14T03:01:01Z	"Because I have a separate login system in place, I no longer wanted the initial admin user created during setup in the system. I revoked the admin users super admin privilege, but noticed that I they still couldn't be removed using the 'Delete' link (there is a check for id not equal to 0 or 1 at line ~100 of {{{wp-admin/network/users.php}}} which prevents deletion, yet no error or anything is shown), however I found that through bulk actions 'Delete' option the user '''can''' be removed since no such checks are in place to prevent it.

Is there any reason for preventing the main admin user to be removed in network mode even if that user has been stripped of the super admin privilege? If so, should this bulk actions removal workaround be patched (and an error displayed when someone tries to delete that user), and if not can the ID check be removed to allow the user to be deleted?"	bananastalktome
Needs Patch	17904	Multisite has more restrictions on user login character set		Multisite	3.0	normal	normal	Future Release	defect (bug)	new		2011-06-27T11:09:12Z	2013-02-12T20:54:04Z	"Multisite has more restrictions on the characters allowed in a user's login name compared to single site. This seems unnecessary and confusing. It was also the root of a recent bug in the importer, see [http://wordpress.org/support/topic/invalid-author-importing-single-wordpress-to-mulitsite-wordpress?replies=21#post-2186667 this forum thread] and the [http://plugins.trac.wordpress.org/changeset/401649 workaround].

I haven't worked up a patch yet since there seem to be a few locations where these restrictions are enforced and I don't know if I have found them all yet:

 - wpmu_validate_user_signup() uses the regex `/[a-z0-9]+/`
 - ms-default-filters.php adds `strtolower` to `sanitize_user`

Relevant: http://mu.trac.wordpress.org/changeset/1689 [12948]"	duck_
Needs Patch	16126	Multisite name conflict check doesn't check for pages.		Multisite		normal	normal	Future Release	defect (bug)	new		2011-01-06T19:11:19Z	2011-01-16T02:18:41Z	"Running WP 3.1-RC2 I made a page off my main site called foobar.

Then I went in and made a sub-site (using SubFOLDERS) called foobar.

The subsite took precedence and there was NO check or warning.

I was able to reproduce this on 3.0.4

Then I went the otherway.  I have a subsite called camels (don't ask).  I went to make a PAGE called camels and it also let me. No conflict check.

Basically you have to add the main blog page names into the banned names list manually, which strikes me as a bit odd.  I can see why checking that would be onerous if someone had 600 million pages (and we all know they do) but forcing people to do it manually seems like a gap.

Need love! :D

This is minor, since not a lot of people have bitched, so clearly we're not running into it YET."	Ipstenu
Needs Patch	23088	Multisite, Subdomains and www		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new		2012-12-30T20:05:33Z	2013-04-28T16:21:25Z	"I installed a WordPress Multisite network (in subdomain mode) on Zend's PHPCloud.com.

Zend does not provide an IP address, recommending a CNAME instead. CNAME records are not allowed on the root of a domain, so they recommend using the www subdomain, with a redirect from the root domain to www.

This site can NEVER be accessed on the naked domain; it will always be accessed via the www subdomain.

So, I setup wildcard DNS for *.mydomain.com, then created a network on www.mydomain.com. Then, I went to a non-existant subdomain on my network, nonexistant.mydomain.com, and WordPress redirected to www.mydomain.com/wp-signup.php?new=nonexistantwwwmydomaincom.

The correct behavior is to redirect to www.mydomain.com/wp-signup.php?new=nonexistant

The fix for this is in wp-includes/ms-settings.php, replace line 89 with:

{{{
$site_domain = preg_replace( '|^www\.|', '', $current_site->domain );
$destination = 'http://' . $current_site->domain . $current_site->path . 'wp-signup.php?new=' . str_replace( '.' . $site_domain, '', $domain );
}}}

Also, on the registration page at the bottom it says:

""The site you were looking for, http://nonexistant.www.mydomain.com/ does not exist, but you can create it now!""

The fix is in ms-blogs.php, line 53:

{{{
$url = preg_replace( '|^([^\.]+://)(?:www\.)?|', '$1' . $blogname . '.', $url );
}}}"	jkhoffman
Needs Patch	23755	Old /files/ support in new installs		Multisite		normal	minor	Awaiting Review	defect (bug)	new		2013-03-13T13:54:10Z	2013-03-15T13:35:17Z	"I moved a blog to a new network that using new upload folder system. Problem is: old /files/ links  that using ms-files.php are not working.

My temporary fix:
Added in .htaccess:

{{{
# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

}}}

Added ms-files.php:
{{{
define( 'BLOGUPLOADDIR', WP_CONTENT_DIR . ""/uploads/sites/{$current_blog->blog_id}/"" );

}}}
above of:

{{{
$file = rtrim( BLOGUPLOADDIR, '/' ) . '/' . str_replace( '..', '', $_GET[ 'file' ] );
}}}

Solution is working but I am not happy because it needs to edit core files. Is this working as intended? If it is, what is proper way to define BLOGUPLOADDIR for ms-files.php without breaking anything or editing ms-files.php"	unsalkorkmaz
Needs Patch	22860	Site list in Network Admin shows Master Site where each network site should		Multisite	3.5	normal	normal	Awaiting Review	defect (bug)	new		2012-12-11T19:27:54Z	2012-12-11T19:56:49Z	When in the Network Admin area, hovering on My Sites should present a list of all the active sites on the network, however, while it shows the correct number of sites, the name and links all point to the master site, and not the network sites. This behaviour is not reflected when on the child sites and acts correctly. It is only when in Network Admin.	thewanderingbrit
Needs Patch	21837	Site search for a domain by text fails in subdomain installs of multisite with www in primary domain		Multisite	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-08T00:30:50Z	2013-04-28T16:21:22Z	"To reproduce:

1) Create a subdomain network install where the main site's domain contains www
2) On the Network Admin->Sites search for an existing site based on the domain name, such as some* to find somedomain.domain.com.
3) Search returns ""No sites found."" even when the site exists and was searched for using a valid technique.

I've tested the problem on Apache and Nginx servers, with Twenty Eleven as the theme on the main site, and network activated plugins.  Existing sites can never be found by domain name.

Subdomain installs in a network are allowed where the main site is www.domain.com. DOMAIN_CURRENT_SITE in wp-config.php points to www.domain.com.  But blogs.domain stores the domain of a multi-site site named somedomain as somedomain.domain.com (without the www).

As a result, any site search for a domain based on text (the name of the domain) fails because of how the query is built on lines 70-73 of wp-admin\inludes\class-wp-ms-sites-list-table.php.  A search for some* produces a query that searches for some%.www.domain.com instead of some%.domain.com; the result is that nothing is ever found.

Searches based strictly on site ID work fine.

Possible fixes: 1) leave as is but warn that subdomain network installs where the primary domain includes www will have a broken site search (not ideal) and encourage no www on primary site of a subdomain network install or 2) check if the primary domain contains www and strip it out prior to building the query (ideal)."	frisco
Needs Patch	19995	Slow down of access to Multi-Site Admin area when Upgrading to 3.3.1		Multisite	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-02-08T22:57:26Z	2012-02-09T00:14:42Z	I've done a search and didn't see a trouble ticket for this so I wanted to post it and see what the feedback looked like. With the upgrade to WordPress 3.3.1 I've seen a very big slow down of access to the Admin area for both the Network sites as well as the Network Admin. I thought it was my server lagging at first or maybe an issue with me having to clean up my MySQL server but I've heard from others whom I know that also run Multi-Site installs having the same problem as well. One gentlemen's client thought his site had even been hacked because of the amount of time it was taking to get to the admin area but after running the necessary security tools it was realized that the server was secure but the lag did exhist. Any thoughts?	bastosmichael
Needs Patch	23748	Suggest rewrite rules on IIS Network (Multisite)		Multisite	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-12T18:23:35Z	2013-03-12T18:23:35Z	"Server: Microsoft IIS - 8
Wordpress: 3.5.1 (multisite)

On subfolder install, suggest for web.config is:
{{{
<?xml version=""1.0"" encoding=""UTF-8""?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name=""WordPress Rule 1"" stopProcessing=""true"">
                    <match url=""^index\.php$"" ignoreCase=""false"" />
                    <action type=""None"" />
                </rule>
                <rule name=""WordPress Rule for Files"" stopProcessing=""true"">
                    <match url=""^([_0-9a-zA-Z-]+/)?files/(.+)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""wp-includes/ms-files.php?file={R:1}"" appendQueryString=""false"" />
                </rule>
                <rule name=""WordPress Rule 2"" stopProcessing=""true"">
                    <match url=""^([_0-9a-zA-Z-]+/)?wp-admin$"" ignoreCase=""false"" />
                    <action type=""Redirect"" url=""{R:1}wp-admin/"" redirectType=""Permanent"" />
                </rule>
                <rule name=""WordPress Rule 3"" stopProcessing=""true"">
                    <match url=""^"" ignoreCase=""false"" />
                    <conditions logicalGrouping=""MatchAny"">
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsFile"" ignoreCase=""false"" />
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsDirectory"" ignoreCase=""false"" />
                    </conditions>
                    <action type=""None"" />
                </rule>
                <rule name=""WordPress Rule 4"" stopProcessing=""true"">
                    <match url=""^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""{R:1}"" />
                </rule>
                <rule name=""WordPress Rule 5"" stopProcessing=""true"">
                    <match url=""^([_0-9a-zA-Z-]+/)?([_0-9a-zA-Z-]+/)?(.*\.php)$"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""{R:2}"" />
                </rule>
                <rule name=""WordPress Rule 6"" stopProcessing=""true"">
                    <match url=""."" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""index.php"" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>		
}}}

On sudomain install, it is:
{{{
<?xml version=""1.0"" encoding=""UTF-8""?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name=""WordPress Rule 1"" stopProcessing=""true"">
                    <match url=""^index\.php$"" ignoreCase=""false"" />
                    <action type=""None"" />
                </rule>
                <rule name=""WordPress Rule for Files"" stopProcessing=""true"">
                    <match url=""^files/(.+)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""wp-includes/ms-files.php?file={R:1}"" appendQueryString=""false"" />
                </rule>
                <rule name=""WordPress Rule 2"" stopProcessing=""true"">
                    <match url=""^wp-admin$"" ignoreCase=""false"" />
                    <action type=""Redirect"" url=""wp-admin/"" redirectType=""Permanent"" />
                </rule>
                <rule name=""WordPress Rule 3"" stopProcessing=""true"">
                    <match url=""^"" ignoreCase=""false"" />
                    <conditions logicalGrouping=""MatchAny"">
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsFile"" ignoreCase=""false"" />
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsDirectory"" ignoreCase=""false"" />
                    </conditions>
                    <action type=""None"" />
                </rule>
                <rule name=""WordPress Rule 4"" stopProcessing=""true"">
                    <match url=""^(wp-(content|admin|includes).*)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""{R:1}"" />
                </rule>
                <rule name=""WordPress Rule 5"" stopProcessing=""true"">
                    <match url=""^([_0-9a-zA-Z-]+/)?(.*\.php)$"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""{R:2}"" />
                </rule>
                <rule name=""WordPress Rule 6"" stopProcessing=""true"">
                    <match url=""."" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""index.php"" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>	
}}}

I think that Wordpress Rules for files and Wordpress Rule 4 and 5 should follow same rules than htaccess suggest. 
When following actual suggest in a subfolder installation, I get an HTPP Error in call to sub site, error is always reproductible for me - can you confirm.

A fix could be to add a subdir replacement rule {R:1} for subdomain install and {R:2} for subfolder.

Implementation in the network.php file (adding $iis_subdir_replacement_12):
{{{
$iis_subdir_replacement = $subdomain_install ? '' : '{R:1}';
$iis_subdir_replacement_12 = $subdomain_install ? '{R:1}' : '{R:2}';

$web_config_file = '<?xml version=""1.0"" encoding=""UTF-8""?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name=""WordPress Rule 1"" stopProcessing=""true"">
                    <match url=""^index\.php$"" ignoreCase=""false"" />
                    <action type=""None"" />
                </rule>';
				if ( is_multisite() && get_site_option( 'ms_files_rewriting' ) ) {
					$web_config_file .= '
                <rule name=""WordPress Rule for Files"" stopProcessing=""true"">
                    <match url=""^' . $iis_subdir_match . 'files/(.+)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""' . $iis_rewrite_base . 'wp-includes/ms-files.php?file='.$iis_subdir_replacement_12.'"" appendQueryString=""false"" />
                </rule>';
                }
                $web_config_file .= '
                <rule name=""WordPress Rule 2"" stopProcessing=""true"">
                    <match url=""^' . $iis_subdir_match . 'wp-admin$"" ignoreCase=""false"" />
                    <action type=""Redirect"" url=""' . $iis_subdir_replacement . 'wp-admin/"" redirectType=""Permanent"" />
                </rule>
                <rule name=""WordPress Rule 3"" stopProcessing=""true"">
                    <match url=""^"" ignoreCase=""false"" />
                    <conditions logicalGrouping=""MatchAny"">
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsFile"" ignoreCase=""false"" />
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsDirectory"" ignoreCase=""false"" />
                    </conditions>
                    <action type=""None"" />
                </rule>
                <rule name=""WordPress Rule 4"" stopProcessing=""true"">
                    <match url=""^' . $iis_subdir_match . '(wp-(content|admin|includes).*)"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""' . $iis_rewrite_base . $iis_subdir_replacement_12 . '"" />
                </rule>
                <rule name=""WordPress Rule 5"" stopProcessing=""true"">
                    <match url=""^' . $iis_subdir_match . '([_0-9a-zA-Z-]+/)?(.*\.php)$"" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""' . $iis_rewrite_base . $iis_subdir_replacement_12 . '"" />
                </rule>
                <rule name=""WordPress Rule 6"" stopProcessing=""true"">
                    <match url=""."" ignoreCase=""false"" />
                    <action type=""Rewrite"" url=""index.php"" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>';
}}}

Sorry for my english :)

regards


"	guy_fr
Needs Patch	21919	Theme Customizer: loading preview with FORCE_SSL_ADMIN does not work		Multisite	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-18T14:17:28Z	2012-09-18T14:17:28Z	"When FORCE_SSL_ADMIN is configured theme customizer JQuery will try and load the theme preview over ssl and get a 302 redirect error.

The path is

https://site.com/?customize_messenger_channel=preview...

redirects to

http://site.com/?customize_messenger_channel=preview...

since site is non-SSL."	Jasonheffner
Needs Patch	23750	Uploads go into subdirectory install of WordPress		Multisite	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-12T22:10:59Z	2013-03-13T02:26:44Z	"In upgrading a few sites to WordPress 3.5 and then giving WordPress its own directory (`wp/`), we continually see the uploads end up in `wp/wp-content/blogs.dir` instead of `wp-content/blogs.dir`.

For the time being as a work around we have enabled a network wide plugin that consists of 

{{{

function ms_upload_fix($uploads) {
	$uploads['path'] = str_replace('/wp/', '/', $uploads['path']);
	$uploads['basedir'] = str_replace('/wp/', '/', $uploads['basedir']);
	return $uploads;
}
add_filter('upload_dir', 'ms_upload_fix');

}}}

We do have `WP_CONTENT_DIR` defined and assume it should use this if set."	jondavidjohn
Needs Patch	12832	Use the same data type for site statuses	database	Multisite	3.0	normal	normal	Future Release	defect (bug)	new		2010-04-03T19:48:20Z	2012-01-31T17:50:59Z	"For status archived we use:

{{{
archived enum('0','1') NOT NULL default '0',
}}}

Fo the others:

{{{
public tinyint(2) NOT NULL default '1',
mature tinyint(2) NOT NULL default '0',
spam tinyint(2) NOT NULL default '0',
deleted tinyint(2) NOT NULL default '0',
}}}

Shouldn't we use the same data type for the others?
"	ocean90
Needs Patch	21691	WPLANG not settable in multisite if there are no language files		Multisite		normal	normal	Awaiting Review	defect (bug)	new	close	2012-08-26T11:16:24Z	2012-10-12T13:26:56Z	"I got a plugin running on a multisite and there is definitely something up with the translation.

I tracked the problem down to the WPLANG option in `http://localhost/<subsite>/wp-admin/options.php` being empty. I tried to update it, but it keeps reverting to blank. So down the line the issue with get_locale() looking for the WPLANG value in the site_options and then defaulting back to en_US because it's not picking it up from the wp-config.php defined WPLANG.

I'm assuming that the defined WPLANG in the wp-config.php does not apply in multisite instances. The plugin is only enabled on the separate blog instance, and I changed the translation in wp-config.php after the install if that has anything to do with it.

Simple filter to force the locale in the plugin for the moment:


{{{
function modify_locale(){
    return 'de_DE';
}
add_filter('locale','modify_locale');
}}}


I hope someone can reproduce this issue."	foxinni
Needs Patch	24211	WPMU works with example.com but not sub.example.com		Multisite	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-04-28T12:00:24Z	2013-04-28T12:19:00Z	"Installtion 1:
I created a WPMU installation on http://example.com/ domain with http://example.com/site/ link structure and it works just fine. Users can register new blogs and they can access them using respective links they chose.

Installtion 2:
I created another WPMU installation on http://test.example.com/ domain with http://test.example.com/site/ link structure and it works just fine. Users can register new blogs and they can access them using respective links they chose.

Installation 3:
I created yet another WPMU installation on http://test2.example.com/ and it works (I can access main theme, Dashboard etc.) but as soon as user registers new site under http://test2.example.com/site/ - it returns 404 not found in admin panel and when I try to view this website. I copied .htaccess etc. correctly, paths are correct. In case of this installation I also redirected this subdomain to another server.

DNS:
test2.example.com - record A - 000.000.000.000 (IP of the second server)

I bet that it generated invalid .htaccess content but I may be wrong."	Looimaster
Needs Patch	13554	Wordpress MU canonical link redirect failure	markjaquith	Multisite	2.9.2	normal	normal	Future Release	defect (bug)	new		2010-05-26T16:30:37Z	2010-11-13T08:02:46Z	"This problem manifests itself in Wordpress '''MU''' 2.9.2, but '''not''' in Wordpress 2.9.2.

In the MU install where blogs are subdirectories, canonical redirects work correctly for the subdirectory blogs, but not for pages on the root blog.

For example, [http://silverwarethief.com/essays/] is a sub-blog in the wordpress MU install. If you alter that link to [http://www.silverwarethief.com/essays/] wordpress MU will correctly redirect the browser to the canonical url.

However, this does not work with pages on the root blog. [http://silverwarethief.com/about/] is a page on the root blog. If you go to that link, you will correctly find yourself at the ""About"" page. If you then alter the link to [http://www.silverwarethief.com/about/] you will be redirected to the main page of the root blog, not the ""About"" page.

I have seen this behavior manifested on more than one MU install.

"	rundi
Needs Patch	22370	dynamic_sidebar does not consider switch_to_blog		Multisite	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-11-06T04:33:23Z	2012-11-06T04:33:23Z	"On the main site of my WordPress network, I have a header that I would like to show on all other sites of the network. The main site uses the parent theme and all of the other sites use child themes. In header.php of the parent theme, I'm using ''switch_to_blog'' function to load Navigation Menus from the main site in the header of the other sites. This is working perfectly.

'''The Problem'''

I also have a sidebar in the header that I would like to manage on the main site as I do with the navigation menu. Unfortunately, this doesn't work at all because dynamic_sidebar function does not take into consideration switch_to_blog. I get no output instead of showing sidebar from main site.

'''Others with same problem'''

Boone Gorges did a good job of explaining this problem on WordPress Stackexchange on the question titled: [http://wordpress.stackexchange.com/questions/48123/sharing-dynamic-sidebars-across-multisite-blogs Sharing Dynamic Sidebars across Multiple Blogs]. "	tarasm
Needs Patch	13689	multisite noblogredirect set, 404 error result not sending proper info with IIS		Multisite	3.0	normal	normal	Future Release	defect (bug)	new		2010-06-02T01:01:31Z	2012-08-14T08:32:10Z	"Scenario.  With NOBLOGREDIRECT specified as the main sites url, the 404 errors and the bad blog url are supposed to go what is specified as the location in the noblogredirect define.

The bug is the 404 errors are *not* pointing to what is specified in the noblogredirect, the 404 errors (that are not bad blog urls) are triggering an IIS error response and not redirecting.  

When it's done triggering the IIS error it then uses the web.config to transfer to the main site.

Besides this bug.

This tells me 2 things, this tells me that the method/behavior of this is wrong and should be looked at.  *if* wordpress knows the difference between a bad blogurl and a 404 error page, the 404 error *should* go to the 404 template, however in the past WPMU versions it did not do that it went straight to the mainsite as well.   It *should* go to the 404 template and since it knows the difference it should be coded a such.

1) Bad subdomains should go to the specified noblogredirect define.
2) 404 error pages should go to the 404 page template for the theme.

Not to mention that the bug in question *is* that the 404 error itself is not redirecting to it's intended location to begin with.



"	Frumph
Needs Patch	20861	switch_to_blog() breaks custom post type permalinks		Multisite		normal	normal	Awaiting Review	defect (bug)	reopened		2012-06-06T22:30:53Z	2013-04-15T12:18:49Z	"When using switch_to_blog() and custom post types, there are very strange results when calling the_permalink() or get_permalink().  For reference, we'll say the root site is blog1 and the second site containing the posts is blog2.

Using this code inside the loop:

{{{
switch_to_blog( $post->blog_id );
get_permalink();
}}}


If the post type is not registered on the current blog, the permalink given will be sitename.com/blog2/slug - when clicking it as href, it brings you the first instance of that slug in the database.

If the post type is registered on the current blog, the permalink given will be sitename.com/blog2/blog1/post-type/slug - this link will 404.

Related issue: #14992"	sickhippie
Needs Patch	16201	when updating a multisite blog subblogs getting 404 error		Multisite	3.0	normal	normal	Awaiting Review	defect (bug)	new		2011-01-12T14:01:28Z	2013-05-08T20:26:43Z	When I run an update at my multisite, I get 404 error when I try to view a post. This error resolves when I change or update the permalinks at each sub blog. But it is annoying to do so when you have hundreds of sub blogs. 	YogieAnamCara
Needs Patch	24312	wordpress 3.4.1 muti-sites image has not appear in time on safari sometimes		Multisite	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-11T01:11:37Z	2013-05-11T01:11:37Z	"I'm running muti-sites wordpress with nginx, and test on safari (chrome is fine).

A very important thing is, the image is upload by administrator.

I found sometime some image has not appear immediately, I was just thing a about network trouble before, but I found the rule today.

the rule is:

enter the page, image shown.
refresh the page(Command + R), image disappeared.
refresh again, image shown.
again again, it disappeared.
loops....
NOTICE: disappeared is means that's not apear immediately: loaded the page about 2 second later, the image could be loaded.

---- solution ----

When you refresh the page, safari send a image request to server with HTTP header `HTTP_IF_NONE_MATCH` and `HTTP_IF_MODIFIED_SINCE`.

Because of this is a mutiple site, nginx rewrite the request to ms-files.php to process it. ms-files.php found the image has not been modified, so it's response 304 with no content.

The bug is, the ms-files.php has already set `Content-Length` header before decided to response 304, so the response header going to be 304 with no content and `Content-Length > 0`. After that, safari was down.

Fixed the bug by add `header( 'Content-Length: 0' );` to wp-includes/ms-files.php line 79.

{{{
     75 if ( ( $client_last_modified && $client_etag )
     76     ? ( ( $client_modified_timestamp >= $modified_timestamp) && ( $client_etag == $etag ) )
     77     : ( ( $client_modified_timestamp >= $modified_timestamp) || ( $client_etag == $etag ) )
     78     ) {
     79     header( 'Content-Length: 0' );
     80     status_header( 304 ); // new line
     81     exit;
     82 }
}}}

     "	ericdum
Needs Patch	12993	'get_current_blog()' and/or 'current_blog_id()' function?		Multisite	3.0	normal	normal	Future Release	enhancement	new		2010-04-14T08:32:48Z	2010-08-24T22:42:11Z	"I posted this over in the mu forums but realize it is pretty dead over there and may be better mentioned here:

http://mu.wordpress.org/forums/topic/17568?replies=2

It would be a great help to easily get the current blog's id as in 'current_blog_id()'. I searched the entire wordpress 3.0 and mu code and it is not mentioned anywhere.

'get_current_blog()' might imply something more complex that returns all a blog's info, which would be nice too.

But in the short term... 'current_blog_id()'?

People are currently having to call global variables to use $wpdb, $current_site and/or $blog_id. I feel all of these are messy and pretty generic variables to be using within theme or plugin files."	martythornley
Needs Patch	13743	Ability to change default theme for network sites		Multisite	3.0	normal	normal	Future Release	enhancement	reopened		2010-06-06T05:44:12Z	2010-12-06T20:16:41Z	As stated in summary. I use WP 3.0 RC and I've found out that there is no way to set up a theme which should be used by default for newly created sites in network. Even then I disable all the themes except the one I want to be used, WP still set thentyten as theme for newly registered site. The only solution I was able to find is to change theme description and name to twentyten and delete all other themes. It's so simple to let administrator choose default network theme, and this option is present in many other CMS.	fuwaneko
Needs Patch	24138	Add Constant control for Multisite.		Multisite		normal	normal	Awaiting Review	enhancement	new		2013-04-19T15:53:06Z	2013-04-22T07:58:41Z	"Not sure if this should be tagged as feature request or enhancement.

WordPress is now making quite an extensive use of constants (like AUTOSAVE_INTERVAL , WP_POST_REVISIONS or EMPTY_TRASH_DAYS ) that are configured in wp-config.php in the form of define('EMPTY_TRASH_DAYS', 1 ); .

Right now, AFAIK , there is no way to define those variable on a site-to-site (or blog-to-blog) basis in Multisite mode.

So for example if one wants his main blog to empty trash every 3 days, while another blog to be set to 5 , or even allow and enable DEBUG_MODE on a certain blog , while keeping it disabled in others , is not currently possible (again, AFAIK) .

Now, I am not sure this should be done with constants , or with some new functions , or simply in some settings implementation, or even with some kind of a blog-based config.php for each blog ,  but it sure would be a necessary layer of control to have ( if indeed the Multisite feature is to be kept alive and expanded ..)


"	krembo99
Needs Patch	20075	Add action hooks to wp-activate.php in WP network		Multisite	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-02-19T11:55:26Z	2012-02-19T11:55:26Z	"Similar to the hooks in wp-signup.php:

do_action( 'before_signup_form' );
do_action( 'after_signup_form' );

these hooks should be added to wp-activate.php:

do_action( 'before_activate_form' )
do_action( 'after_activate_form' )

Purpose : allow signup and activate pages to be built/styled in a similar way.
"	gdvwp
Needs Patch	20592	Add hooks to New Site form in Dashboard		Multisite		normal	normal	Awaiting Review	enhancement	new		2012-05-01T18:53:16Z	2012-07-20T19:03:02Z	"WordPress provides hooks for altering the wp-signup.php form that users use to create new sites on a MultiSite network.  Using these, we developed a plugin that adds fields there for people to indicate some other information about their site. (specifically, to choose a topic)

However, there are no such hooks available on the New Site form available to network admins via the dashboard for some reason.  This means that I am not able to append the extra form fields here that I can on the wp-signup.php page.

There should be similar (or identical) hooks used here so the New Site form can be modified in a similar way and be consistent with the wp-signup.php form."	MadtownLems
Needs Patch	22701	Allow the use of SITEURL and HOME constants for Multisite Installations		Multisite		normal	normal	Awaiting Review	enhancement	reopened		2012-12-03T21:21:26Z	2012-12-03T22:02:13Z	"This is a proposal to allow the use of the SITEURL and HOME constants, as we do with single site installations.

My proposal would be to follow the naming conventions put forward by the database schema for multisite installations.

Example for a constant override of the siteurl and home option for blog_id 3.

{{{
#!php
define('WP_3_SITEURL', 'http://example.com');
define('WP_3_HOME', 'http://example.com/wp');
}}}

"	jondavidjohn
Needs Patch	23349	Be able to suppress registration redirect for multisite in wp-login.php		Multisite	3.5.1	normal	normal	Awaiting Review	enhancement	new		2013-02-01T01:29:35Z	2013-02-01T02:06:55Z	"Currently I commented out the following lines in wp-login.php.  But I should be able to use a filter.  Maybe test the result  'wp_signup_location' filter if false do not exit.  Easy, and seems to annoy many people.
{{{
case 'register' :
    /*  AJB Comment out
	if ( is_multisite() ) {
		// Multisite uses wp-signup.php
		wp_redirect( apply_filters( 'wp_signup_location', network_site_url('wp-signup.php') ) );
		exit;
	}
	*/
}}}"	aberglas
Needs Patch	12030	Better Options for New Registrations		Multisite		normal	normal	Future Release	enhancement	new		2010-01-26T00:23:07Z	2012-04-18T17:13:58Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/872



At the moment when new users register, there are very few options and not many plugins available.. It would be nice if the administrator could :

1) Allow passwords to be set during registration, rather than having it sent by email.

2) Make Email Verification optional.

3) See the users who haven't confirmed their registrations, and resend the confirmation emails from the admin area..

4) User Moderation : Make it easier to kick out users and delete spammers.. 

5) Invitation Codes (Optional): Allow the admin to create invite codes, which he can distribute, so that the mu install is well knit social community.

I know this is pretty much doable, but there lacks any good solution at the moment.
"	wpmuguru
Needs Patch	19879	Better caching for get_dirsize		Multisite	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-01-23T15:42:59Z	2012-01-24T23:54:25Z	"In a multisite install, when trying to determine whether a site has exceeded its storage quota, WordPress will scan through a blog's upload directory and sum up the file sizes, by running {{{filesize}}} against each one. With a large number of files, this can significantly slow down the upload process or certain portions of the Dashboard.

{{{get_dirsize}}} has transient caching in place but this is a single cache entry for all folders. It might be better if WordPress has a separate cache entry for each folder and was invalidated based on context so that get_dirsize does not need to be run constantly on older, unchanged directories as frequently."	batmoo
Needs Patch	12145	Enhance activation process to improve integration with site theme	westi	Multisite		normal	normal	Future Release	enhancement	new		2010-02-06T07:10:13Z	2012-01-11T11:21:04Z	"wp-activate.php creates many notices on load due to theme hackery

an example to start:
{{{
Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\comment-template.php on line 777

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\comment-template.php on line 794

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\general-template.php on line 1588

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600
Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\post-template.php on line 431

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\post-template.php on line 1172
class=""page page-id- page-parent logged-in"">
}}}

the problem is, that wp-activate.php attempts to simulate a normal WordPress page, the problem arrises that when the header is included and/or custom code in the theme runs on the header, that the no-existance of the current post id (NULL) causes most of the WordPress functions to complain, as they're expecting a correct post object to be returned.

2 options
 1. Update all API function to move to {{{ if ( ! $_post = get_post(..) ) return false; - This should probably be done anyway
 2. Improve the hackery to allow displaying custom pages such as wp-activate.php more transparently.

Furthur to #2, this might involve creating a page in the database which the API functions can access directly, the activate site page would then become a real page in the eyes of WordPress."	dd32
Needs Patch	17948	Enhancements to the login and registration forms	wpdavis	Multisite	3.2	normal	normal	Awaiting Review	enhancement	new		2011-06-30T16:25:01Z	2013-01-14T19:27:28Z	"I would like to propose a significant overhaul of the registration and login forms for 3.2, which I'd be happy to take on. A few things that I think would be helpful:

Combine registration processes for multisite and single-user into one form on one page.
Allow the registration and login to be templatized — no reason this should be for MS only.
Standardize filters, actions and variables between MS and single-user when at all possible.

A few related tickets:

#17904
#17306
#17085
#16866
#16411
#17630"	wpdavis
Needs Patch	14172	Implement $scheme in site info in ms-sites edit site		Multisite	3.0	normal	normal	Future Release	enhancement	new		2010-07-01T22:45:33Z	2010-07-03T19:17:45Z	"In WordPress 3.0 with Network enabled, if you were to click:

Super Admin -> Sites -> Edit (next to any site) and then change any of the Site Options i.e. wp_2_options the changes don't save. 

We're running a secure environment and need Siteurl to be HTTPS instead of HTTP. Changing all the parameters to https and clicking Update doesn't save the changes."	firmdot
Needs Patch	12043	Infinite redirect if using a port number		Multisite		normal	normal	Future Release	enhancement	new	close	2010-01-26T17:28:32Z	2012-02-06T10:53:23Z	"MU Trac Ticket: http://mu.trac.wordpress.org/ticket/189



While setting up my new blog I found that WordPress? MU continuously re-directed me to the same URL (occurs in the if statement on line 9 of wp-signup.php). This was being caused by wpmu-settings.php on line 10. The variable $domain has the port stripped from it, which causes line 84 to return no result when it queries the database.

WP MU is installed at  http://some.host.address:8080/blogs on my machine. VHOST is false.
"	wpmuguru
Needs Patch	23270	Links are not updated when changing a multisite path		Multisite	3.5	normal	minor	Awaiting Review	enhancement	new		2013-01-23T07:37:24Z	2013-01-25T04:28:14Z	"When changing the path of a site under a network install, URIs are not updated in post_content.

I know this can be achieved with search and replace plugins (and that this is how regular WP installs work), but the wording on the edit site page makes it appear as if WP should be updating this for you with; ""Update siteurl and home as well."", where the ""as well"" makes it sound as if other elements on your site will be updated regardless.

I'm not sure if the best approach would just be a re-wording of this area, or if implementing a function to update post_content when this is modified is the way to go."	Clorith
Needs Patch	17164	More elegant handling of site 'archive' options for MultiSite		Multisite	3.1	normal	normal	Awaiting Review	enhancement	new		2011-04-18T15:08:50Z	2012-12-16T06:14:58Z	"Right now you have a few options with MultiSite blogs

1) Spam
2) Deactivate
3) Archive
4) Delete

Spam is easy to understand, and should be marking the admin and site as spam. Delete ditto, hi.

Deactivate and Archive are weird though and almost seem backwards.  Deactivate means to turn OFF (like deactivating a plugin).  Archive implies that you're making a site read-only.

Right now, if you change a site to 'deactivated' it actually shows up as DELETED and the front end has the message ""This user has elected to delete their account and the content is no longer available.""  Clearly the verbage on the network/sites.php page needs to be updated (and perhaps the front end to 'This site has been deactivated.' to be consistant).

If you 'Archive' a site it kicks it to a paler pink in the sites.php page (though the 'Archived' text is white and nigh impossible for me to read) and the front end says ""This site has been archived or suspended.""

It's rather illogical there.  Archive SOUNDS like it should be making things read-only (and turning off commenting and posting if possible).  Otherwise it should just be 'Suspend', and at that point, why have two options that pretty much do the same thing from the front-end perspective?"	Ipstenu
Needs Patch	12002	Multisite should not lock the root blog into using a /blog prefix		Multisite	3.0	normal	normal	Future Release	enhancement	new		2010-01-25T03:51:06Z	2013-01-29T19:26:55Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/409

I don't think WPMU should lock the root blog into using a /blog prefix on permalinks. Currently, the /blog on the beginning of permalinks is hardcoded.

I realise this was probably added to stop conflicts when not using a VHOST solution, but when using VHOST to put other blogs into subdomains, why lock the root blog's permalinks as such?

Could the /blog requirement be removed if VHOST is 'yes'?
"	wpmuguru
Needs Patch	11869	Multisite upgrade notice at wpmu-upgrade-site.php isn't steadily visible.		Multisite	3.0	normal	minor	Future Release	enhancement	new		2010-01-11T22:03:14Z	2011-12-15T23:59:25Z	"When upgrading (Site Admin > Upgrade) wordcamp.org, it started upgrading each site and flashing a list of 5 sites at a time that had been upgraded (too quickly to really be read beyond the first item in each list). When it flashed through all the screens, it showed ""All done!"" and nothing else. 

Preferred UX would be to list the sites in order as they are upgraded but in a single persistent list rather than in flashing batches of five, and to show the all-done message on the same screen, with the list of everything that has been upgraded. It would be good to have the text appear at bottom of list (in sequence) but to also drop in an alert message at top of screen. "	jane
Needs Patch	14988	Site admins should be allowed to add existing users without also enabling creation		Multisite		normal	normal	Future Release	enhancement	new		2010-09-29T07:08:11Z	2010-10-27T08:11:35Z	"Blog admins are allowed to add users to their multisite blog when the ""add new users"" network setting is turned on.

Unfortunately this allows them to both add existing users, and create new users. There should be a way, potentially just with a filter versus an option, to limit that to only add existing users, and prevent the creation of new users without going through the public registration process.

Use case: WordPress.com does exactly this.

Alternative use case: WordPress.org uses a pretty crazy SSO setup. We should not be allowed to create new users through the admin, but it would be very helpful to allow administrators to add users to a blog without going through the network admin (or asking a super admin).

Real world use case: Any blogging network like WordPress.com, or crazy synchronized login system like WordPress.org, would want this."	nacin
Needs Patch	18225	Sub-blog on Network site redirects to wrong URL for user registration		Multisite	3.2.1	normal	critical	Awaiting Review	enhancement	new		2011-07-23T03:35:06Z	2012-11-04T06:00:36Z	"When a user clicks on the '''register''' button of a sub-blog, it redirects the user to the signup form on the primary blog, which means they end up creating an account with it instead of the sub-blog.

When the user tries accessing the sub-blog login after activation, they are denied access because the registration took place with the parent blog instead.  There's also no way to transfer users to another blog.

This issue sounds similar to the one in #16866 , but it's not a feature request, instead it's a bug.

My test case is:
network blog is installed in sub-directory, such as '''http://mydomain.com/blogs/'''.
A sub-blog is created at say '''http://mydomain.com/blogs/my-sample-blog/'''.
I register a new user account with the sub-blog, which takes me to '''http://mydomain.com/blogs/wp-signup.php''' instead of http://mydomain.com/blogs/my-sample-blog/wp-signup.php.

Running on Ubuntu 10.04, Apache 2, PHP 5.3, WordPress 3.2.1."	amereservant
Needs Patch	23358	Switch to a usermeta key for email confirmation in Multisite		Multisite	3.0	normal	normal	Awaiting Review	enhancement	new		2013-02-01T13:54:05Z	2013-02-01T13:54:53Z	"Background: #23146

In `send_confirmation_on_profile_email()`, an option is used to store the new email: [[BR]]
http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/includes/ms.php#L238

A usermeta key should be used instead."	SergeyBiryukov
Needs Patch	19497	The 'My Sites' menu is redundant for users with just one site		Multisite	3.3	normal	normal	Future Release	enhancement	new		2011-12-10T07:03:58Z	2012-01-27T20:53:06Z	"When a user only belongs to one site in a multisite install, they're shown a 'My Sites' menu. All of the items in this menu in this scenario are redundant (both in the admin area and when viewing the site) as all four menu items can be accessed from other menus in the toolbar.

Users shouldn't be shown this menu unless they belong to two or more sites.

I know we're on RC2 but I'd love to get this into 3.3 because it looks a bit silly."	johnbillion
Needs Patch	16990	WP Multisite doesn't use custom db-error.php	tmuka	Multisite	3.1	normal	minor	Awaiting Review	enhancement	new		2011-03-28T19:19:46Z	2011-07-18T01:23:14Z	"I suppose this is a feature request. I don't see a way to configure a Multisite install to use the same wp-content/db-error.php file as a single wp site install uses. Instead where the db is down the page dies on ""Error establishing database connection"" wrapped in an <h1>.

It could be a complication of using the HyperDB plugin, but it appears that on line 104 of wp-includes/ms-settings.php when the db is down get_blog_details() obviously fails and wp-includes/ms-load.php:ms_not_installed() is called. Unfortunately ms_not_installed() does not redirect to db-error.php, and instead dies, returning
$title = /*WP_I18N_FATAL_ERROR*/'Error establishing database connection'/*/WP_I18N_FATAL_ERROR*/;

Obviously i could hack in a call to wp-includes/functions.php: dead_db() in ms-load.php, but i try to avoid any core hacking to make upgrades easier.

Does anyone have a suggestion for overriding this behavior cleanly? perhaps something in wp-WP_CONTENT_DIR/sunrise.php ?

I suppose if somebody else is interested in the simple fix, here it is. In ""function ms_not_installed"" on line 224 of wp-includes/ms-load.php, insert dead_db();
like this...

{{{
function ms_not_installed() {
dead_db(); //hacked this in so we can get use our custom db-error.php
}}}

The bottom line is that now the visitor will potentially see a more friendly error message when the db or db table is unavailable."	tmuka
Needs Patch	23808	allow multisite to match bare URL		Multisite	3.5	normal	normal	Awaiting Review	enhancement	new		2013-03-18T13:33:07Z	2013-04-01T09:39:30Z	"Currently, when matching the requested URL to a blog, the ""domain"" and ""path"" are used together. When there is no match, no blog will be selected. $path can never be interpreted as just ""/"".

This makes it impossible to have multiple domains working from the root ""/"" pointing to separate blogs.

The attached patch makes this possible.

A little more in-depth explanation can be found here:
http://wordpress.org/support/topic/allow-multisite-to-match-bare-url?replies=4
"	fuentez
Needs Patch	13752	multisite loop		Multisite	3.0	normal	normal	Future Release	enhancement	new		2010-06-07T04:17:57Z	2010-07-17T10:32:56Z	"I've been experimenting with multisite/wpmu and it would be great if there were an actual multisite loop - added ""blog"" parameter to wp_query/querypost. It's possible to emulate a multisite loop with ""switch to blog"", ""get_posts"" and merged arrays, but it requires a hand-written paged navigation adding some arguments to the navigation links. It would be great if there was either a way to directly add blog parameter to the query string."	youngmicroserf
Needs Patch	12013	new user creation features		Multisite		normal	normal	Future Release	enhancement	new		2010-01-25T17:41:04Z	2010-01-27T03:26:35Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/1079

1: there needs to be native ability to select how many blogs each user can have.

2: there needs to be the ability for users to add blogs for users who signed up with out creating a blog and for those who want to add additional blogs to their current list(depending on the blog limit you set in feature request 1 above) from the ""my blogs"" tab in their site admin panel.

3: if the ability to select the number of blogs each user can have is put into place, the option to have the blog auto created to the users name when blog limit is set to 1. ie: user signs up with ""username"" and wants to add his 1 allotted blog it would be auto created using his user name like this example.com/username or username.example.com depending on your settings.

these enhancements kinda all tie together and am surprised they are not currently implemented...
"	wpmuguru
Needs Patch	14862	wp 30 to wpmu - wild card domain - suggestion		Multisite		normal	normal	Future Release	enhancement	new		2010-09-13T18:23:39Z	2012-11-02T22:19:17Z	"im new to wordpress hacking, but i did hit the forums with this.

we could pick up the last 'if' statement from: 

/wp-admin/includes/schema.php 
function populate_network()

the last if :
{{{
if ( $subdomain_install ) 
{
...
...
}
}}}

and paste it to:
/wp-admin/network.php
inside function allow_subdomain_install()

the problem of a last minute Error out would be solved. 

putting it there, and showing a warning in the 1st step itself would be warning enough for the user to go back and get things done right/ check on things again wrt wild carded domain.

again, i am new to wordpress, please do correct me if im wrong 

Warm Regards,
M.
"	msolution
Needs Patch	21910	wpmu_create_user() standardization		Multisite	3.0	normal	minor	Awaiting Review	enhancement	new		2012-09-17T18:03:24Z	2012-09-17T23:36:26Z	"There seems to be some inconsistencies between wpmu_create_user(), create_user(), and wp_insert_user(). The former two are wrappers, and do different things but potential to consolidate and clean up some old code.

Per Nacin:
>nacin: wpmu_create_user() should probably just go away.

>nacin: fairly useless function

>nacin: by default, it looks like wp_insert_user() would create a role-less user.

>nacin: as would wp_create_user()

Looking at wp_insert_user() it sets the default role if none is provided, where wpmu_create_user() would actually delete the default roles and caps. 

Although, I'm not really sure there's a use case where you'd be using both the wpmu_new_user and user_register hooks simultaneously so possibly depreciate the former in favor of the latter. 

One real issue with wpmu_create_user is that it returns false instead of the WP_Error object which is probably not desired since the error could be useful. The false return is used in wpmu_activate_signup() to either set the returned ID or create it's own WP_Error. 

Lastly... documentation for create_user says it returns the ID, but it looks like it could potentially also return a WP_Error object. Didn't test, but possible documentation fix there. 
"	ryanduff
Needs Patch	20286	Allow direct use of top level domains in multisites		Multisite	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-03-23T05:46:00Z	2012-11-20T12:00:28Z	"Most people installing the multisite would need top level domains and not the subdomains. The domain mapping plugin doesn't really fit in cause it depends on creating aliases and mappings and works on redirects. Separation is important which i guess is the main purpose of multisiting.

I see default WP setup allows you to rename the site URL once its created. So I did, renamed the subdomain into main domain and got into redirect loop problem. After some searching, it turned out the problem was caused by DOMAIN_CURRENT_SITE in wp-config being static. So I changed it to $_SERVER['SERVER_NAME']. This though solved the looping problem but got one more issue. Now going into child site's dashboard requires you to re-login cause of cookie not being set for all child top level domains.

Let's be it - not all people need the subodmain mutisites as you may notice on the forums. Meanwhile, if there's a workaround for setting up cookies for all of the top level sites when logging into network, please advise!

The multisite codex wiki itself tells the same - as a matter of fact it shows a screenshot having a top level domain as a wp site and that was the main reason why I went on choosing mutisite."	mickylmartin
Needs Patch	14569	Assign plugins on a per-site-basis		Multisite	3.0.1	normal	normal	Future Release	feature request	new		2010-08-09T09:35:55Z	2012-05-31T19:44:33Z	It's possible to assign themes per site with WordPress Multisite. However it isn't possible to assign plugins per site. Some plugins are only used for the mainsite and I don't want them to be visible in subsites.	ChantalC
Needs Patch	14215	MultiSite: Add new > different username from blog title		Multisite	3.0	normal	normal	Future Release	feature request	new		2010-07-06T18:09:37Z	2010-10-28T06:38:44Z	"I would like to request that the current system for adding a new blog site be expanded so that as admins, we can specify a different username that's unrelated to the blog title. That is, in '''Site Admin -> Add New''', at the bottom of the page, add a new field specifically for the username. For that matter, it would be useful to also have a field to be able to specify the password, and perhaps a little checkbox that allows you to optionally prevent an email from being sent. These features are really useful when you're manually adding sites for employees, students, and the such.

I had provided a fix for wpmu 2.8.4 at one point (with a better explanation and details), you can see the thread here: http://mu.wordpress.org/forums/topic/12945

An example of the final result: http://img696.imageshack.us/img696/2551/addblogwordpress.png"	Person
Needs Patch	22816	Multisite WP_Query		Multisite		normal	major	Awaiting Review	feature request	reopened		2012-12-07T18:25:10Z	2012-12-08T18:28:12Z	Multisite has no global search functionality, and suppose I want to show on the home page of my main site posts from all the other sites in my network... I don't have a multisite wp_query functionality. Sure, I can use switch_to_blog, but that only works for results from each blog, one by one, suppose I want navigation on my results, suppose I want to make a most recent posts widget, or any type of functionality where I want to query posts from the entire multisite, custom post types, pages, all the wp_query class has to offer only works for each individual site so far, It would really help as a huge feature for WordPress multisite	ciapci
Needs Patch	12017	Press This multiple blog support		Multisite		normal	normal	Future Release	feature request	new		2010-01-25T17:57:19Z	2010-01-27T03:26:26Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/1092

A WordPress MU user may wish to pass external content into the MU authoring interface. Authoring interfaces such as  Press This currently do not support the selection of a target blog for which the currently logged in user has  edit_posts capability.

 Internet Explorer 8,  Google Reader, and bookmarklet functions currently help pass new post information into an authoring tool such as Press This, but requires a pre-determined URL template to pass along new actions.

Good: http://wordpress.org/wp-admin/press-this.php

Bad: http://*.wordpress.org/wp-admin/press-this.php

Currently a user can add a bookmarklet or IE Accelerator on a per-blog basis. It would be a much better user experience if he or she could target a predictable URL endpoint on the MU install.
New URL ¶

adminurl/press-this.php

Point to the MU install's main admin handlers and let it handle user state.
Possible handling ¶

    * Redirect user to Press This interface of their primary blog with query params intact.
    * Add a new stuffbox to the post interface sidebar with a <select> drop-down if currently logged on user has edit_posts capability on more than 1 blog. Default blog selected.
    * Select box value is passed in at post. No URL redirects on new option selection. 

Possible downsides ¶

Writing a new post from somewhere outside direct blog context could have consequences.

    * Plugins attached to target blog not loaded. 

Next Steps ¶

Once there is agreement on the best approach I can submit the appropriate patch.
"	wpmuguru
Needs Patch	20377	Show notice that site Network Admin is viewing is disabled		Multisite	3.0	normal	minor	Awaiting Review	feature request	new		2012-04-06T14:47:29Z	2012-11-17T16:15:48Z	"In Multisite, site admins can click ""delete site"" from their Tools menu, but this actually just sets it to disabled.  If a Network Admin tries to view the site, they can still view it just fine.  This can be pretty confusing/misleading.  I think it would be an improvement if while a Network Admin is viewing a Disabled site, that a message is displayed along the lines of:

This site is currently Disabled. [re-enable link]"	MadtownLems
Needs Patch	18025	WPMU New Blog Default User Role		Multisite	3.2	normal	normal	Awaiting Review	feature request	new		2011-07-07T12:26:50Z	2012-11-17T15:53:53Z	"When I using WP Multisite as Network Admin and creating a new blog, The new user to the blog will get role: Administator for the new blog.

I want to add in wp-admin/network/settings.php a setting for ""New Blog Default User Role"". Where the Network Admin can set the default role for users to new blogs.

So you can set that if you creating a new blog and enter one e-mail address the user will get the role you have in your settings, so you can set users to new blogs to be example subscribers instead of Administrators like today.

Exactly as the plugin http://wordpress.org/extend/plugins/new-blog-default-user-role/ but this one is not so good."	jontelm
Needs Patch	14941	dynamic unloading and loading of plugins		Multisite	3.0	normal	normal	Future Release	feature request	reopened		2010-09-22T20:13:37Z	2010-10-06T20:18:33Z	"The short:
If I'm blog 1 and I switch_to_blog(2), I'm still running in the environment of blog 1.  All blog 1's activated plugins are active, and not all of blog 2's plugins necessarily are.

The long:
I first ran into the problem trying to get Subscribe2 (S2) to work well with Site Wide Tags (SWT).

SWT basically works like this:
When someone makes a post on their blog: switch_to_blog(aggregrate_blog_id); 
wp_insert_post(...); 
restore_current_blog();

S2 says that whenever someone inserts a post, to send an email alert out.

With both of these plugins enabled, a post always generates TWO emails, regardless of whether S2 is active on the aggregate blog.  The same is true for any behavior that triggers on a new post being created (such as automated tweeting, etc).

I feel that, if I'm really switching to that blog, I should be running more comprehensively as it.  That is, with its plugins active, and none of its un-activated plugins active.

The examples of conflicts I gave are blog behavior, and are more or less just annoying, but I could easily see this causing unforeseen security flaws as well."	madtownlems
Needs Patch	16291	user role drop down inaccurate on ms-sites.php		Role/Capability	3.0.4	normal	normal	Future Release	defect (bug)	new		2011-01-18T21:23:32Z	2011-01-18T22:39:11Z	"If a user has been assigned a role and an individual capability, the user list doesn't show the correct role for the user. 

This is the scenario to replicate this issue.  User is currently given one role (ie. editor).  Then some plug-in adds an individual capability (db has role and cap serialized - order is important). You then go and change the role(ie. publisher) of that user using ms-sites.php (db has cap then role serialized). When you return to ms-sites.php (not immediate page load, but refresh, or new page load), the drop down menu for the user in question will show Administrator. It appears, that ms-sites is pulling the first item from the serialized list, and since it isn't a role, it doesn't know how to populate the drop down.

This is a particular issue, if you go to the page to change any information not related to user permissions.  Anyone whose accounts had the extra cap would suddenly become Administrators.

There may be other scenarios where this same things happens, but as best I can tell this is the particular scenario that is causing me problems.

Also, I do realize that there is a potential for user->role->cap overhaul in a future release, but since it doesn't seem to be part of the 3.1 milestone, I thought this should be fixed. 

As another note, the users.php page seems to handle this scenario a bit better.  The solution might be over there.   "	hughestm@…
Needs Patch	13765	It's unclear why a max upload size limit is set		Upload	3.0	normal	normal	Future Release	defect (bug)	new		2010-06-07T13:39:17Z	2010-11-13T08:06:49Z	"When you reach your allowance for file uploads in a multisite environment, it's not clear why WP will advertise a tiny upload size limit.

For instance, if you can upload up to 10MB of files, with a 2M file size limit, and you've already uploaded 9MB, WP will erroneously report that you can upload up to a 1MB file.

This can lead a multisite newbie to look into php ini files and the like, in order to identify which obscure setting is messing things up, instead of heading straight to the multisite options.

Instead, WP should report that the maximum file size is 2MB, and highlight in a follow-up line that only 1MB is available until the quota is reached."	Denis-de-Bernardy
Needs Patch	12720	Delete user and hook confusion when deleting users in Multisite		Users	3.0	normal	normal	Future Release	defect (bug)	new		2010-03-26T12:42:59Z	2010-06-23T17:24:58Z	"Currently:
The hook ''wpmu_delete_user'' fires when deleting user in Super Admin->Users.
The hook ''remove_user_from_blog'' when deleting user under site Users->Authors & Users.
In standard WP:
The hook ''delete_user'' is called when deleting users it should be the same in MultiSite when deleting from Super Admin->Users.
Or add new hooks and deprecate previous.
''delete_user_from_network'' for when deleting a user totally.
''delete_user_from_site'' for when deleting a user from a specific site. This is hook also then fires in non-MultiSite mode since that then corresponds to one site."	andreasnrb
Needs Patch	13339	Hook on ms-users.php		Users		normal	normal	Future Release	enhancement	new		2010-05-11T11:45:37Z	2010-05-17T15:14:25Z	"On WP 3.0 it is possible to add new users as Super Admin, but they do not really assign each instance. So it would be useful when creating the user, if you have a selection of instances that are created and then selecting one with the checkbox where the user should get access.

Maybe it is possible to add a hook for add own fields, similar the possibilies on user-edit.php for profile fields."	bueltge
Needs Patch	12032	Additional Option of Site Admin -> Options -> Allow new Registrations.	kallumamaji	Users	3.0	normal	normal	Future Release	feature request	reviewing		2010-01-26T00:29:42Z	2011-12-29T09:29:57Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/799

Right now the 4 options are: Disabled - noone can register a new account or blog Enabled - blogs and user accounts can be enabled (at the same time as the request) Only User Account - Only a user account can be created. Only Logged in User - Cannot create a user account but those who can log in can create a blog.

Need a 5th option for Create User Account and Allow blog creation if logged in.

With the 5th option it will allow new registrations., but only allow them to request a new blog if they are a valid online user after registration.
"	wpmuguru
