#MAMP WORDPRESS MULTISITE INSTALL#

htaccess file, this is the example one for SUBFOLDER install if you started your multisite with WordPress version 3.5 or higher: RewriteEngine On To read define( 'SUBDOMAIN_INSTALL', false ) If you want to go from subdomain to subfolder, you first need to change define( 'SUBDOMAIN_INSTALL', true ) Wait, do I really need to say, please back up your site BEFORE you go any further?ĭone? Alright, let’s go. (You’ll find all the information you need in the “Multisite Network Administration” section of the WordPress codex.) Since we only had language appreviations for site names (de for German, en for English,…) I felt we would be safe to go. The only reason for this, however, seems to be that you might run into conflicts between page names and actual site names. It’s been a while and I never doubted this. When we first created the network, we used the subdomain install because it said right there in the WordPress codex that you should not use the subfolder approach if your website had been set up for longer than a month. So after checking all options, I realized everything would be so easy if we just could change the network from the domain based network (“subdomain” install) it was into a path based one (“subfolder” install). Today, with wanting to have SSL on all sites, this slowly grew into a nightmare. A few years ago we changed a multilingual blog into a WordPress Multisite network using MultilingualPress for the multilingual part.

Mamp wordpress multisite