“…WordPress network must use sub-domains.”

I meant to say, could I avoid that message, and instead GET the option to have the network in regular child dirs?

(Just saw that it was possible to edit these posts. ?? )

That’s utterly wild. I’ve got the beta for a multi-site install with subdirectories just fine. Two domains, too.

Can you screenshot that error? I’m thinking it’s not actually a WP error.

Hi. Thanks for the reply. I would post a screen shot, but I deleted that install (and cleared out the database) and when I reinstalled everything, that error/message wasn’t generated. (Sorry.)

FWIW, when I got that message, it was on a WP installation that I had previously a) physically moved on my server from a subdir to the root (as per the recommendations for multisite use) and b) then upgraded both to beta2 (from b1) and then to multisite use. So who knows what might have gone wrong or unexpectedly in that likely too-clever process.

But I’m pretty sure the message was from WP, as the options to use sub-dirs or sub-doms were missing, and it simply informed me that I had to proceed with sub-doms — that is, it seemed pretty official.

This probably acounted for the problem I asked about in this post…

https://www.ads-software.com/support/topic/398601?replies=1

…which also didn’t recur once I did a proper fresh install.

Hmm. Oh well.

(As an aside, it’s such a pleasure dealing with this kind of stuff with WP than it was with Movable Type. Now if only there was a reliable way to import from MT, to go along with WP3’s cool new features….)

I did my MT to WP conversion in the 1.x days of WP, so all my info is out of date, but…

Try this post: https://www.simonecarletti.com/blog/2009/02/movable-type-to-wordpress-importer-utilities/

Force old install to use sub-directory:

add_filter( 'allow_folder_install', create_function( '', 'return true;' ));

see: https://zeo.my/force-wordpress-network-to-use-sub-directories/

Hi,

I have been attempting to extend a single WordPress install into a WordPress network and get the same message when setting up the network.

“Because your install is over 1 month old, the sites in your WordPress network must use sub-domains.”

The solution posted by Zeo above works perfectly on my test site, but as I intend rolling this out to a client’s website soon, I just wondered if there was any more info about why WP websites over 1 month old cannot by default use the directory setup?

Can anyone explain this a bit more, or direct me to more info?

Thanks in advance.

John
??

Ah, I sorted this out later. It’s because subfolders could conflict with other page urls you already have. The way urls for subdirectories work, the first blog gets urls for pages like domain.com/pagename, which could possibly rub elbows badly with domain.com/subfolder you see.

There’s another way to do it, by changing the wp-config like for subdomains to false.

It’s a temporary warning that was put in there for release, which will probably change at some point in the future. It’s not that it *can’t* be used, it’s just then *when* you do it, the /blog/ is placed in the permalinks of the main blog.

And on older established blogs, users get testy when you make changes that break all their exisiting links. ??

Thanks for the replies people, much appreciated.

So if I am understanding correctly, provided I don’t have any permalinks named the same as any potential sub-directories that I may want to create, I should be ok?

e.g. as long as I don’t have a permalink https://www.example.com/blog/ then I could conceivably create a site in my network called ‘blog’, so so on?

Yes BUT.

If you use subfolders, then WordPress automatically takes the /blog/ folder for blog posts in your main site.

You can get rid of it, but it’s allocated to start with.

So is the best approach to avoid creating a sub-site/folder called /blog/ ?

Out of interest, how is ‘blog’ allocated and how is it removed?

I’m having the same problem updating to multisite, I get the ” your install is over 1 month old” msg.
I get further in, and add a site, it says I must go nameofsite.domain.org, even after I chose the subdirectory method.

Actually I found this on the net, not sure if it works, have not tried it yet. https://zeo.my/force-wordpress-network-to-use-sub-directories/

Force WordPress network to use sub-directories
2:08 pm
By zeo
Categories

* Text

Tags

* wordpress

In WordPress 3.0, we have the ability to create a network of sites. But if your install is over 1 month old, the sites in your WordPress network must use sub-domains because of permalink problems with “/blog/” from the main site. This is how you can force the sites in your WordPress network to use sub-directories during the Network installation process.

Add the following lines to your current activated WordPress Theme’s template file, preferably your Theme’s template functions.php file:

add_filter( ‘allow_subdirectory_install’,
create_function( ”, ‘return true;’ )
);

You can remove the lines above once you done enabling the Network feature.

Creating this into a plugin is not an option, since all plugins are required to be deactivated before enabling the Network feature. Please read on how to Create A Network in the WordPress Codex and ticket #12931 for more information on why it is block by default.

Or just set it up using subdomain then immediately go back to the confgi file and change subdomains true to false. then snag the new rewrite rules. (yes, it’ll change them).

Thanks for the link, rescatista !

It works perfectly, just activated multiple sites on my WP3.0 install (hosted by 1and1).

Haven’t come around to building the second site and messing around with permalinks…. will let you know if there is any effect.