Remove “/wordpress/” from multi-site URL

Moving you to the mutlisite forum..

If you have the install in a folder called /wordpress/ that’s why.

unfortunately, the multisite feature will not work if you try and strip that from the URLs. It has to build them off where WP is installed.

So move my install to the root check wp_config and i should be ok, or do i need to go though the multisite setup again to get alll the database enties correct?
I have no operating sub sites yet, still testing so wouldn’t be a problem

Yeah, it’d be less work to reinstall it in the root.

I did it nicely with virtual hosts (apache config below):
(the second line allows for subdomain blogs)

You may need to updated a few settings in database and .htaccess to match the changes.

<VirtualHost *:80>
ServerName blogs.mysite.org.uk
ServerAlias *.blogs.mysite.org.uk

DocumentRoot /var/www/blogs/wordpress/
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/blogs/wordpress/>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
</Directory>
</VirtualHost>

WordPress developers should remove the /wordpress folder from the zip file. A lot of newbies install wordpress as is, under the wordpress folder.

I have seen gazillion blogs under the …/wordpress/… folder (live sites).

Charybdis – Speaking as someone who curses every time she unzips a file and finds everything dumped there in the folder and not it’s own subfolder … no ?? There are good reasons for this, least of which, you won’t accidently overwrite your files if you unzip in the wrong folder.

But if I want to use the “extract” feature of the cpanel file manager, then I must upload wordpress as a zip file. Then I go to the file manager, and simply extract it on the server. Otherwise uploading the unzipped wordpress files takes forever.

But since wordpress is in the wordpress folder, first I have to unzip it locally, then zip it again now without the wordpress folder.

And as I said, a lot of people make the mistake and install their live site under the wordpress folder.

I’d argue that cpanel’s file manager is one of the worst tools to use to manage your files. If you’re at that point, you may as well just get a decent FTP client (they’re free), and be happy.

Why? Cpanel File Manager is the best! ?? It is more convenient than a FTP client. And it can extract zip files on the server side. Not sure that FTP clients can do this?

One more point: some shared hosts don’t support SFTP, but they provide SSL login into cpanel, so in this case the only secure way to manage file is the cpanel file manager.

And it can extract zip files on the server side. Not sure that FTP clients can do this?

Sure can. Well, some can, some can’t, but still, yes, it can be done.

Cpanel File Manager is a graphic, web based, FTP interface. That’s really it. It’s slower than FTP, too, since it’s tunneling over HTTP. It doesn’t always show hidden files (so good luck editing your .htaccess on older versions). Also if your PC gets a virus, it’s more likely your password will be scoped via your BROWSER than your FTP client.

You can drag and drop with FTP clients, sync between your computer and the server, etc etc. More robust ??

One more point: some shared hosts don’t support SFTP, but they provide SSL login into cpanel, so in this case the only secure way to manage file is the cpanel file manager.

Any host that doesn’t give me SFTP isn’t worth my money. I don’t care their reasons why, SFTP (and SSH) are staples of web development. If you’re not going to give me one (or preferably both) of those, I’m out. There’s just too much limitations on cpanel file manager to make that a viable option for more than the hobbyist. And if you’re that low techy, you may as well use Fantastico. (I say this as someone who started her experience with WordPress via a Fantastico install – It’s not a terrible place to start from.)

But if I want to use the “extract” feature of the cpanel file manager, then I must upload wordpress as a zip file. Then I go to the file manager, and simply extract it on the server. Otherwise uploading the unzipped wordpress files takes forever.

But since wordpress is in the wordpress folder, first I have to unzip it locally, then zip it again now without the wordpress folder.

And as I said, a lot of people make the mistake and install their live site under the wordpress folder.

And when I do this on cpanel sites, I upload the zip to the same level as the public_html folder, because I *know* that the files are in a folder in the zip.

then after unpacking, I see a public_html folder and a wordpress folder. So I start renaming. ??

We can’t go changing package download because it doesn’t suit your workflow.

Charybdis – Speaking as someone who curses every time she unzips a file and finds everything dumped there in the folder and not it’s own subfolder … no ?? There are good reasons for this, least of which, you won’t accidently overwrite your files if you unzip in the wrong folder.

Here is the million dollar question… why not rename the /wordpress folder inside the zip to /blog?

There are probably tens of thousands live blogs under the /wordpress public URL, and this is ugly! People are lazy and/or not savvy enough to rename/remove the default wordpress folder from the zip.

Here is the million dollar question… why not rename the /wordpress folder inside the zip to /blog?

Not everyone wants it in blog any more than they do in wordpress.

There are probably tens of thousands live blogs under the /wordpress public URL, and this is ugly! People are lazy and/or not savvy enough to rename/remove the default wordpress folder from the zip.

And herein lies my angst of making WordPress so easy.

I think that, if you’re going to run a website, you (not you personally, you-whomever-is-running-the-website) ought to have some understanding of what’s going on. That means, yes, I expect you to learn how to move and rename files. And I expect you to learn how to FTP files up and down, extract zips, and follow the directions from the Codex.

We all started out the same. Not a single one of us was born with the inherent knowledge of how to drive a car. But we learned. Running a website is, similarly, a learned skill. If you don’t like how yours looks, you learn how to change it. Or you hire someone else to do it. But I feel you should at least make the effort to learn.

If you’re too lazy, I got nothing for you. If you ask for help, I try to help, I try to show you docs on how to do things, and I’ve even spent time hunting up FTP tutorials. And yes, at the end of the day, I know there are people who just can’t do this and can’t get it. And to them I say ‘Make good friends with a WordPress talented person and send them lots of cookies and beer.’ That’s what my neighbor did ??

Not everyone wants it in blog any more than they do in wordpress.

That’s highly unlikely. How many users do use WordPress as a blogging platform? And why would anyone create a public folder called “wordpress”, except this is a category page?

So do you think this URL was structured by design? https://johncbogle.com/wordpress/

Think about another issue. In the previous versions of WordPress, the checkbox “don’t use the noindex,nofollow meta tag” during the install wasn’t ticked by default. So a lot of people made their blogs noindex,nofollow.

If we would follow your logic, that checkbox is fine, why cannot read the user who installs WordPress? But that checkbox is now ticked by default in the latest version.