What's the core logic of Multisite ?

Ah… I see, thanks 🙂

Could you point me out the plugin for the multiple top-level domain ?

Just to be sure, for you, there is no distinction between “top-level domain” and “same level folder” ?

My case is really:
– mysite.com/fr/ <!– One site, multisite installed from here
– mysite.com/en/ <!– another site

But I’m on the same domain, no ? (mysite.com)

I must consider my case as 2 distincts domains ?

You mean because it need an .htaccess to parse the URI and determine the route to the correct blog ?

What if I put & tweak the .htaccess in mysite.com/ ?

Why your saying their’s no way arround ? Technically, it’s possible.
The idea is to forward all request from / to /fr/.

Request:
mysite.com/en/article12

Parsed by mysite.com/.htaccess

Then the following rewrite would occur:
mysite.com/fr/en/
to
mysite.com/fr/

And then the mysite.com/fr/.htaccess file would thread the request again, not even knowing that it has been previously rewrited.

So the /.htaccess file should handle 2 exceptions cases:
– The main WP installation ( in this case /fr/ ) as we don’t want the result to be /fr/fr/
– The files in / , in my case that would be a static negative condition. So, do not rewrite everything that doesn’t match: (\/fr\/(.*)|\/en\/(.*))

My not a pro with rewrite, but I’m sure that’s possible, and I’ll prove your “No way around it.” statement to be wrong 😉

I’m still investigating and testing stuff, but I’m now able to display the /en/ site correctly, by using my rewriting of /en/ to /fr/en/.

I’ve done alot of try & error, so it’s not a definitive solution, but it turned out that I’ve been able to solve part of my problem by doing the following mod:

Near the line 67 of the file ms-settings.php, I’ve remplaced this:
$blogname = htmlspecialchars( substr( $_SERVER[ 'REQUEST_URI' ], strlen( $path ) ) );

By this:

$reqUri = isset($_SERVER['REDIRECT_URL']) ? $_SERVER['REDIRECT_URL'] : $_SERVER[ 'REQUEST_URI' ];
		$blogname = htmlspecialchars( substr( $reqUri, strlen( $path ) ) );

This first path will load the good site, but the “article fetching” will not be ok. You’ll have the good site loaded, but it will report the error message “article not found”.

To solve that part, I have to modify classes.php, WP::parse_request() method, near the line 161, replacing:
$req_uri = $req_uri_array[0];

By:
$req_uri = isset($_SERVER['REDIRECT_URL']) ? $_SERVER['REDIRECT_URL'] : $req_uri_array[0];

Now I have the front page displayed correctly in the good site. Next problem: all the links are using the /fr/en/ path. So it must be related to some kind of ROOT_PATH_URL constant or something like this.

I’m still investigating.

Note: My admin panel is accessible in both /en/wp-admin/ and /fr/en/wp-admin/ , but as all the link redirect to /fr/en/, I’m redirected there as well after the login.

TLDR: It’s broken, I’m fixing it.
——-

Think out of the box; WordPress is a blog system, and we’re not all using WordPress as a CMS, but often as a part of larger sites.
I have a site at the root of the domain, I can’t ovewrite it with a wordpress installation. What I could do is to create a /blog/ folder, and then install it inside, but that would be against the SEO planning of my client.

I might go in alot of trouble, but for me, it only point out that there is a trouble in the system. I’m on the way for fixing a problem. And listening to you, I’m not the first who seem to ask for that feature, so I don’t think that it’s pointless to get involved in the developpement of that compatibility feature.