Homepage URL without prefix

Hey Matthew,

to avoid any confusion and/or misunderstandings, let’s first get our terminology right.

I assume you have one WordPress multisite installation, with three sites: site.com/en, site.com/fr and site.com/de. Then you also mentioned site.com, so you have another, fourth site – the original (main) site.

Is this correct so far?

Next, what do you mean by this:

site.com is empty by default

The default setup usually is to have the main site (i.e., site.com) serve the default language (meaning: your target audience’s primary language – if that’s applicable), and then have further sites that represent different language versions of your website.
Another (not so common) setup is to have the main site only redirect (which means there’s no content in it).

So, could you please explain in more detail what your current setup looks like, what you want to change, and where you have problems with?

Thanks,
Thorsten

Hey Thorsten!
Thank you for a fast reply and sorry if the explanation wasn’t too detailed.

The main website is on site.com (core multisite) and the rest of the three languages remain on different url’s /en, /fr, /de etc.

I’m trying to have a homepage without the /en/, while the rest of the website has this “prefix”. The site.com is occupied by core multisite.

The easy (but no too clean) way, would be to add the en homepage to core multisite (as sole page), but it seems an awkward solution (in same time I imagine what I’m trying to do, is not less awkward, but that’s not my choice).

So in details, now, when I actually wrote it up and rethinked it, I guess it can’t be done, can it?

Or if I’d switch EN as a main multisite, can I somehow add the “/en/ prefix to all url’s by default, excluding the homepage?

Also, thank you for your time and plugin development. It helped me alot!
I don’t mind if we won’t find solution for this issue, as its – as mentioned – an awkward setup.

How is the main site occupied by core multisite?

From what I understand of your posts, you would like to have everything that can currently be found under site.com/en directly under site.com – is this right?

If so, that’s not a problem at all. site.com is a real site in your network. It can (and should) have a MultilingualPress language and content.

Depending on the amount of content, there are several options to achieve this.

Not exactly, if that’d be the case I’d solve it, but its a bit more messy.

The site.com is a network main website, without no content
The site.com/en is a primary language for the website, an individual multisite

I’d like to remain for all posts and page to have an /en/ in URL apart from homepage.

site.com <- homepage for en, but without /en/
site.com/en/post <- urls for posts
site.com/en/page <- urls for pages
site.com/en/content <- urls for all the content apart from homepage

I’m sorry, but I’m afraid I still don’t fully understand this.

You say that site.com/en is an individual multisite (and not a site in your multisite installation). So, did you set up a multinetwork, or two separate installations?
Or is site.com/en a site in your one and only multisite installation?

Next, do you want the home page of your English site, site.com/en, just to be reachable under site.com, and is it okay if the user is actually redirected to the English site?
If so, you can do this by means of a simple redirect theme:

<?php

wp_safe_redirect( get_home_url( $TARGET_SITE_ID_HERE, '/' ), 300 );