It seems like your site has WordPress installed in the root document folder.
Nope. My site has wordpress in /blog and I changed the blog address to be 'root'. It pretends it's in root via the normal method of running WP out of a sub-directory.
If you want to get to my admin side, it's http://domain.com/blog/wp-admin
But no one sees that :) The Blog Address is set to http://domain.com with no trailing slash and yet, it works fine.
What I'm trying to do is place a trailing / on the name of the folder (not the domain name) in the URL entered into the form in Wordlpress Dashboard -> Settings -> General: WordPress address (URL) & Blog address (URL)
That's interesting. I went to a blog I have that IS in a sub-directory entirely, no acting in root, and it too has the trailing slash. It doesn't on the permalinks of one, because I set them to
/%postname%-%post_id% but if I put a / on the end, that shows up too.
But to see it fail to allow a trailing /, enter the more-correct trailing /'d URL and see what appears after pressing "Save Changes".
Right, if I do that it goes back to http://domain.com/subfolder (no /). You are correct, sir :) The thing is that when I go right to the URL, leaving off the /, it redirects to the one with the /, EVEN THOUGH my blog address doesn't have the slash.
It's clearly fine if it's a real subfolder and you only have the problem with an alias (which I'm not buggered to test since I don't have that much free time today ;) ). If you're having this problem with a 'real' sub folder, then it's probably your server since I tested on three different ones and they're all as expected.
I mean, why not just do /public_html/blog/ from the get go?
When the second install is intended for a second user who shouldn't have access to the files of the first, is a good example of when an alias is required.
Huh. I kinda see that, but I've never run into a situation where I had to do that. I mean, if I have two users, each one has their own login and access, and I just have each one use their own public_html folder and handle it on the backend via apache etc.
That said, if you can't do that for some reason, you could make user groups so joe:joe has access to one folder and jane:jane has access to the other. Let unix security handle it.