nginx – Network admin pointing to root as opposed to subdirectory

But didn’t you and I discuss this over here? http://wordpress.org/support/topic/multisite-and-non-root-install?replies=6#post-3099122

I asked “Can I install WP in, say, /blogs and have my various blogs as /blogs/blog1, /blogs/blog2, etc?”

to which you replied “Sure, just install WP in the folder /blogs” along with other notes.

Please don’t say I’ve wasted a few hours…

I just installed it today. Clean install.

So the WP install is in /blogs. Admin is at /blogs/wp-admin/

But Network Admin menu is pointing to /wp-admin/network/ instead of
/blogs/wp-admin/network/

Also, Network Admin->Visit Sites is pointing to our site’s root, instead of /blogs

Right now I’m blanking. Would I have set that when I was editing wp-config? Or was that in a form in the install.

Brand spanking new install so I can start again from scratch…what would I need to do…just drop the tables?

Is the without ‘www’ a huge issue? Our server config automatically redirects all example.com views to http://www.example.com to avoid issues with Google and duplication.

Sorry for the break…was covering the Toronto Film Festival.

Did a reinstall and both the WordPress address and Site address are pointing to example.com/blogs

When I did the Network install the options for wp-config were:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
$base = '/';
define('DOMAIN_CURRENT_SITE', 'example.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

While Network->Visit Site is pointing to example.com/blogs, Network->Edit Site is pointing to:

example.com/wp-admin/network/site-info.php?id=1

What’s the next step to make it point to example.com/blogs/wp-admin/network/site-info.php?id=1 instead?

Also the My Sites->Network Admin links are all pointing to the domain’s root and not /blogs

Thanks.

Okay, I think we’re beginning to talk at cross purposes here.

We went over the part where you cannot (yet) run WP out of a subdirectory and have Multisite, right?

Yes, you mentioned that, but in that case I don’t get your previous answers in http://wordpress.org/support/topic/multisite-and-non-root-install?replies=6#post-3099122

To retiretate, as I did above, I asked “Can I install WP in, say, /blogs and have my various blogs as /blogs/blog1, /blogs/blog2, etc?”

You said, “Sure, just install WP in the folder /blogs” and followed that up with “So if you install WordPress in domain.com/blogs/, then the main site is domain.com/blogs/ and the subsites are domain.com/blogs/site2 and so on.”

So I installed WP in domain.com/blogs

It works. I follow the instructions to set up a network. That works. But there’s an error in the admin links. They point to wp-admin in domain.com, a subdir that does not exist, and not wp-admin in the domain.com/blogs directory, a subdir that does exists.

So I guess the crossed wires in the understanding occurs here. If you say “you cannot (yet) run WP out of a subdirectory and have Multisite” then how can you suggest that I can run multiple blogs in http://wordpress.org/support/topic/multisite-and-non-root-install?replies=6#post-3095243 by saying “So if you install WordPress in domain.com/blogs/, then the main site is domain.com/blogs/ and the subsites are domain.com/blogs/site2 and so on.”

So I guess the ultimate question here is why tell me “the main site is domain.com/blogs/ and the subsites are domain.com/blogs/site2 and so on” if that’s not the case and the admin urls in the dashboard don’t allow it.

I’m not meaning to be difficult. I’m just trying to understand how there are two contradictory answers to the question.

Thanks.

If you install domain.com/blogs then your main URL will forever be domain.com/blogs

I know that. We discussed that. I don’t want anything to be in domain.com and there isn’t anything in domain.com. What I said was that there are links that are pointing to /wp-admin in the dashboard instead of /blogs/wp-admin

Now, if something is sending you to the domain.com/wp-admin URL then what is that something? You just say there’s a link 🙂 there are lots of links.

Mika, I specifically did mention the links that are pointing incorrectly to domain.com. Look 4 messages up, the one that mentions the festival. I say:

While Network->Visit Site is pointing to example.com/blogs, Network->Edit Site is pointing to:

example.com/wp-admin/network/site-info.php?id=1

Other incorrect URLS on the dashboard strip at the top:

My Sites->Network Admin is pointing to domain.com/wp-admin/network/

Next to that series of links, under the name of my Blog Network, Visit Site points to domain.com/blogs but Edit Site points to domain.com/wp-admin/network/site-info.php?id=1 where it should be pointing to domain.com/blogs/wp-admin/network/site-info.php?id=1

Another issue: If I manually enter the URL domain.com/blogs/wp-admin/network/site-info.php?id=1 it incorrectly says the main site is at:

Domain https://domain.com
Path /

I hope this clears things up. WordPress is installed in /blogs. I do not want/expect/think anything should be in /, but somewhere/somehow WP is creating links and configurations that point to /.

I don’t know where our misunderstanding is coming from. You keeping saying things like “You cannot use domain.com in that setup. There will not be a domain.com/WP-admin folder, ever.” I don’t expect there to be. It’s WP that is pointing to URLs in the server root, and I cannot stress enough that based on the installation, I know/expect that everything should be under /blogs. But it’s WP that’s creating the wrong links.