3.0 multi-site > sites > anysite >backend link > bug?

I think I gots a patch:

/wp-admin/ms-sites.php

line 578

remove: $actions['backend'] = "<span class='backend'><a href='" . esc_url( get_admin_url($blog['blog_id']) ) . "' class='edit'>" . __( 'Backend' ) . '</a></span>';

Add: $actions['backend'] = "<span class='backend'><a href='" . esc_url( get_home_url( $blog['blog_id'] ) ) . "/wp-admin/' class='edit'>" . __( 'Backend' ) . '</a></span>';

This seems to fix it and points to get_admin_url being the problem.

I am having this same issue. I would rather not hack core files though. Anyone know a proper fix?

Not seeing it on my installs.

not happening to me either

This is happening to me as well. Previous WPMU install automatically upgraded to WordPress 3.0. Subdomain install. When hovering over the “Backend” link, the current subdomain of whatever site’s backend I am in is what is shown as the link (in the browser’s status bar). I.e. if I am at https://site1.mydomain.com/wp-admin/ms-sites.php, and hover over the Backend link of site2, it shows the link as https://site1.mydomain.com/wp-admin/

I checked the database; the siteurl options are correct for all sites.

Which hosts are you on and do they support wildcard subdomains?

Sounds daft if you’ve upgraded a working site, but I have one of my hosting services now telling me they don’t support them, yet the sites worked under 2.9.2 (some still do) but the auto-upgraded 3.0 sites are having big problems.

I also noticed in the WPMU 2.9.2 readme.txt file (download package root) it has a bit for the allow_override configuration – I can find no mention of that under 3.0 anywhere on wp.org or in the download package files.

… wonders if there’s an issue spawned off that?

For me, this problem exhibits itself both on my dev machine (MAMP) and production machine (Slicehost). On dev, I’m not using wildcard subdomains, as my dev urls are manually entered in /etc/hosts. On production, I am using wildcard subdomains.

Ah, solved for me. I didn’t have the latest version of the Domain Mapping plugin, which fixes this issue. No automatic update notifications on that plugin, since it’s global to the install. Upgrade to 0.5.2 fixed it for me.

See Also:
Domain Mapping Plugin
Another thread discussing this issue

When hovering over the “Backend” link, the current subdomain of whatever site’s backend I am in is what is shown as the link (in the browser’s status bar).

The only times I have seen this happen since my post above, people were running the domain mapping plugin. If you are, update that to the latest.

Otherwise, disable all your plugins – even those in MU plugins, and try again.

@gazouteast – the link still renders properly inside WP regardless of if the sites have wildcards working or not.

You’re right Andrea – it renders correctly but doesn’t go to where it shows – sorry – got mixed up with a different issue