You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This looks integrating, I am faced with a few issues with multi-site instance.
I must define a few globals, such as: VHOST, DOMAIN_CURRENT_SITE, PATH_CURRENT_SITE, SITE_ID_CURRENT_SITE, BLOGID_CURRENT_SITE, WP_ALLOW_MULTISITE, MULTISITE, and just $base
One thing I'm trying is to use the remote database (production or a cloned dev db) - anybody know of a way to prevent the redirect loop for the local instance? For instance, on my production or cloned production dev.db, site_id 1 / blog_id 1 is defined as mydomain.com - and it sees the incoming connection from http://local.instance - so it automatically redirects to http://local.instance/wp-signup.php?new=local.instance - because the multi-site side does this automatically.
I'm wondering, is there a way to prevent this and trick WP into serving the production db with the local.instance URL?
The text was updated successfully, but these errors were encountered:
Hello,
This looks integrating, I am faced with a few issues with multi-site instance.
I must define a few globals, such as: VHOST, DOMAIN_CURRENT_SITE, PATH_CURRENT_SITE, SITE_ID_CURRENT_SITE, BLOGID_CURRENT_SITE, WP_ALLOW_MULTISITE, MULTISITE, and just $base
One thing I'm trying is to use the remote database (production or a cloned dev db) - anybody know of a way to prevent the redirect loop for the local instance? For instance, on my production or cloned production dev.db, site_id 1 / blog_id 1 is defined as mydomain.com - and it sees the incoming connection from http://local.instance - so it automatically redirects to http://local.instance/wp-signup.php?new=local.instance - because the multi-site side does this automatically.
I'm wondering, is there a way to prevent this and trick WP into serving the production db with the local.instance URL?
The text was updated successfully, but these errors were encountered: