Those are the only two Bedrock files you gotta modify. In fact, you don’t really have to modify .env at all. Just application.php.
This should be all it all that’s required, I think:
/**
* Multisite Network
*/
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false); // obv switch this to true if you're using subdomains
define('DOMAIN_CURRENT_SITE', env('DOMAIN_CURRENT_SITE') ?: parse_url(WP_HOME, PHP_URL_HOST));
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
You also have to set up your rewrites, of course.
If you’re still having issues, check to make sure that WordPress didn’t do something super duper “helpful” like add the multisite stuff to the wp-config in your document root (bedrock/web/wp-config.php). lol
WordPress provides you with the .htaccess rules you need when you go to setup multisite. Have you implemented those? Did you not see them? Have you not tried looking for them?
Let us know what you’ve tried to do to troubleshoot this.
This gives us: AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary.
I tried to work with RewriteBase /wp/ which dont gives this LimitInternalRecursion but I am unable to make it stable. Can someone help me how we can RewriteBase correctly to /wp/ with apache?
WordPress provides .htaccess rules for their default folder structure.
Bedrock is changing this structure and moves WordPress into /wp of docroot. I think that’s the reason you added nginx multisite rules in your docs I suppose. I love bedrock and I have no problems with single setups. But I am working on a big multisite project that struggle with the errors I mention with everything I tried all those years. I just kindly ask you for help to find out the correct rules for the minority of us who can’t switch easily to nginx yet.