Wordpress Multisite Application

wmonline

Would appreciate the ability to choose a multisite version of Wordpress during App selection / install.

standardforge

wmonline It's actually crazy to me this isn't supported yet as WP CLI supports multisite commands, and I'm pretty sure Enhance leverages WP CLI significantly. Hopefully this can be rolled out sometime soon.

meditatingsurgeon

to date I have not been able to get multisite to work on Enhance except (subdirectory) when I have imported via Duplicator pro onto a LiteSpeed enterprise server. I not not been able to get multisite subdirectory or subdomains to work with NGINX.

inspiredearth

meditatingsurgeon Hello meditatingsurgeon. I've found almost zero info on Enhance with regards whether it can handle WP Multisite --- Other than this reply from you in this thread.
Is only LiteSpeed Enterprise you've been able to do this on? Am I correct in thinking it's not possible on OpenLiteSpeed, due to lack of a means to make changes to its domain routing, etc.?
I've got a WPMS installation I need to move to Enhance, if it's at all possible. I'll be posting a question on that direct, but figured I'd first tap your shoulder for any insights you might be able to share.
Thank you.

meditatingsurgeon

Working and tested .htaccess rules for WordPress Subdirectory
Recording this here for future reference works with LiteSpeed Enterprise only, WPMU Subdirectory Installations.

When setting up multisite. Make the changes to wp-config as per the network setup instructions.
Use the following .htaccess from the following link instead (had great difficulties pasting the code)

https://gist.github.com/jennimckinnon/71f06f92f1d0396170682cec4285d434

tstrand

Going to chime in here with a solution to addon domains with wordpress multisite on nginx.

The problem is the default location set by the panel for addon domains

location / {
try_files $uri $uri/ =404;
}

This gives all added domains in multisite 404 when requesting /sales for example.

Editing /etc/nginx/sites-enabled/<domain>.conf
With the correct

location / {
try_files $uri $uri/ /index.php?$args;
}

Only works until something changes in the panel or the services are reloaded and the configuration is reverted back.

The solution is to add

location ~ ^/(?!$) {
try_files $uri $uri/ /index.php?$args;
}

to /etc/nginx/vhost_includes/<domain>.conf

This seems to work. Will report back if I notice any problems.

rdbf

tstrand

This is what adding the rewrite rule does already, somewhat hidden under the developer tools.

tstrand

rdbf

Yes but only for the primary domain. All alias domains will get 404 on subdirectory's if you are running wordpress multisite

rdbf

tstrand Yes but only for the primary domain.

Not only for the primary domain, as we're having several websites doing exactly that, multi-site under one Enhance website as subdomains and add-on domains.

Under Developer tools > Nginx, select the right one. Like I said, it's kind of hidden.

tstrand

I stand corrected. That was really well hidden. Thank you

nhybgtvfr

i've had a WP multisite install working on enhance, with no manual changes to the vhost.
using OLS as the webserver though, so not sure how nginx will handle it.

it was a site already working on another panel using apache, copied over into enhance using duplicator pro.
all the extra domains were added to the website as aliasdomains, not additional domains

was done for testing, so all the domains were changed during copying so the live site was unaffected.
the site was already using the plugin domain-mapping by wpmu-dev.

i had to go in to this plugins settings on each subsite and delete the existing mapping and create a new mapping for the changed domain. if migrating a site and keeping the existing domains, i don't think this step would be needed, but can't guarantee that at this point.

only other issue was having to change edit the sites index.php to put the standard content in there.
duplicator had left it essentially blank (just a 'silence is golden' entry in there)
although that may be because i changed the wordpress path during install, as on the live site wordpress was installed into a subdirectory named 'wordpress' in the website root, and i decided to install wordpress directly into the website root folder on enhance.

sam-nlw

nhybgtvfr We recently moved to Enhance and migrated a multisite a few days ago. I must say I was a bit surprised that we didn’t need many rewrite rules. We are using NGINX. These are the rules we are currently using:

`rewrite ^/wp-admin$ $scheme://$host$uri/ permanent;

if (!-e $request_filename) {
rewrite ^/[0-9a-zA-Z-]+(/wp-.) $1 last;
rewrite ^/[0-9a-zA-Z-]+(/..php)$ $1 last;
}

location ~* ^/wp-content/uploads/sites/[0-9]+/gravity_forms/.*.(png|jpg|jpeg|gif|webp)$ {
try_files $uri =404;
access_log off;
expires 30d;
}`