Multisite Admin Panel 'edit post' and other buttons links not valid

Currently it has the following multisites setup:

https://www.domain.com
https://www.domain.com/london/
https://www.domain.com/paris/
https://www.domain.com/berlin/

You mean you have FOUR multisites, or that domain.com is a multisite, and london, paris, and berlin are sites on the network?

Apologies, I meant that https://www.domain.com is the multisite, and London, Paris, and Berlin are sites on the network. Please advise.

Right ?? Makes a difference ??

I changed the network setup of each website to the equivalent of:

Siteurl:www.domain.com/london/
Home:www.domain.com/london/

I’m assuming you did this on a page like /wp-admin/network/site-info.php?id=5 ?

Yes in the settings tab.

That then breaks the back end and the front end as the all paths are the equivalent to https://www.domain.com/london/wp-content/themes/cluboid/images/scroll-top.gif.

But interestingly the backend ‘edit posts’ and other such buttons work.

I know I could copy wp-content into a london directory on the server to fix this issue, but surely this defeats the point of child themes and multisite!?

Also I just tried to create a new site a moment ago just to test it. With the site address as https://www.domain.com/newsite with the user set to my superadmin. It creates it no issue, but then when I then go to this sites dashboard any file wordpress tries to call eg css, javascript etc is a 404 in the console of chrome due to wordpress trying to find files in `https://www.domain.com/birmingham/wp-admin/css/colors.min.css?ver=3.8.1
Failed to load resource: the server responded with a status of 404 (Not Found) `

I’ve also come across this online which seems to be the same problem I’m encountering https://premium.wpmudev.org/forums/topic/network-admin-menu-links-broken-upon-35-subdomain-multisite-install-subfolder-wp-install

You’re not supposed to edit things there. It messes the process up as you’ve just found out. Basically WP doesn’t know what it is anymore.

However the bigger thing is that you totally did it wrong in the first place.

On /wp-admin/network/site-info.php?id=5 on the EDIT tab, I see this:

THAT is what it’s supposed to look like. You want it to say london? You change that to london. You do not, under any circumstances, go into the “Settings” tab and edit it there, because THAT is a super advanced, please don’t mess with it unless you understand how to repair databases, section.

Home and site URLs should be https://example.com/london/ HOWEVER you do not change it in the back end of settings. You change it in the edit tab.

Hi Mika,

After taking your advice I completely wiped the server starting afresh following the install step by step.

On the creation of each site on the options I did as you told me and did not change the settings tab, just in the edit tab setting the path to /london/ and hey presto! It’s still the same issue.

The wordpress backend for london is still 404’ing it’s own files looking in https://www.domain.com/london/wp-includes/js/filename

This is driving me crazy. Of course I could just create a subfolder on the server and put in the files it’s trying to pull in but surely this would defeat the point of one install???

I appreciate your help thus far.

You can see here what I’m referring to in regards to broken links on these two screen shots

https://s29.postimg.org/alhukxhk7/image.jpg

https://s22.postimg.org/qe7qwo3kx/debug.jpg

As mentioned above, we’ve followed the setup step by step, and have multisite setups on other projects (although in subdomain format). Even for highly skilled php programmers we cannot see why this would be?!

Can you show us your .htaccess and custom definitions in wp-config.php? My guess is an .htaccess problem.

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress

/* Multisite */
define(‘MULTISITE’, true);
define(‘SUBDOMAIN_INSTALL’, false);
define(‘DOMAIN_CURRENT_SITE’, ‘www.domain.com’);
define(‘PATH_CURRENT_SITE’, ‘/’);
define(‘SITE_ID_CURRENT_SITE’, 1);
define(‘BLOG_ID_CURRENT_SITE’, 1);

Your .htaccess is slightly different than mine. The lines that are different affect the 404 urls you see. I got my setting from the WP page – https://www.domain.com/wp-admin/network/setup.php

My .htaccess looks like this:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

You may want to try my .htaccess on your system. If you do remember to backup your current ones. My bet is that this will fix your 404s… hopefully =)

So what I told you was the right way to edit it.

On the creation of each site on the options I did as you told me and did not change the settings tab, just in the edit tab setting the path to /london/ and hey presto! It’s still the same issue.

Here’s the real question. Why do you need to do this at all?

Look, if I want a site named london, I make a site named london and I leave it the heck alone! There’s no logical reason to rename a site.

The wordpress backend for london is still 404’ing it’s own files looking in https://www.domain.com/london/wp-includes/js/filename

That’s where it’s supposed to look!

jkhongusc’s htaccess is correct, by the way. Yours is an older version.