Network Admin - Site Search breaks Row Action Links

[Ipstenu]

​http://blog.dearbornschools.org/webmaster/files/2011/03/networkadmin_issue.swf

Basically.

If you go to wp-admin/network/sites.php and try to mark a site as spam or anything on the hover-over links, it's fine.

BUT if you SEARCH for a site, it CHANGES those row action links from

/wp-admin/network/edit.php?action=confirm&action2=spamblog&id=11......

to

/SEARCHVALUE/wp-admin/network/edit.php?action=confirm&action2=spamblog&id=11......

Which blows up in your face.

Worse is if you use a wildcard, then you get SEARCHVALUE% as the URL.

Here's the best part. It only happens on subFOLDER multisite. Works perfectly fine on subdomain.

I was able to reproduce it on two separate subfolder installs, one with no plugins at all.

Forum post wherein we sorted this out: ​http://wordpress.org/support/topic/network-admin-user-and-site-admin-links-dont-work-31

(I can't repro the user issues he had, but I can the blog search)

I'm having same/similar issue.

I go to Network Admin, Search sites. Search for a site with a wildcard i.e. photo* the results show up just fine, HOWEVER after clicking on any of the site options for the found site (i.e. Edit, Spam, Archive, Delete) the URL changes to:

www.mydomain.com/photo%/wp-admin/network/site-info.php?id=32

Tested with Subdomain from [1und1.de] Result: Same as subFOLDER!

see patch!

Patch works for me on subfolders (cannot repro on subdomains like nerx can, but it doesn't BREAK anythign I can see).

That part of code is only executed for directory installs so I am sure subdomain installs will not have this problem.

Typo introduced in [16161].

(In [17496]) Avoid mangling the current site path variable with the search query. props greuben, fixes #16720 for trunk.

(In [17497]) Avoid mangling the current site path variable with the search query. props greuben, fixes #16720 for the 3.1 branch.

This patch didn't make it into the 3.1 download on wordpress.org. I've got two MultiSite installations running upgraded 3.1 installations and this bug is still present. When I upgraded, I manually deleted the entire wp-admin folder and replaced it with the new copy from the wordpress.org download. If I apply this patch, they work fine.

Replying to tmoorewp:

This patch will be out with 3.1.1?

Yes. :)