That's the $baseurl, one of the most important variables. Some one in the past decided to add the slash there and not with the paths. I don't see an easy fix, if any.

Good luck

Actually the slash at the end is not part of the $baseurl value. I forget the selected URL field for that blog, but each blog goes by "index.php/blogname" and gets a trailing slash after the blog name.

I don't know where that gets tacked on, but if it gets removed from there then I THINK permalinks will break because it would be missing the slash between the blog name and the rest of the permalink stuff.

Sorry nelsonguirado but I didn't even notice that detail when you reminded me to make sure your URLs matched what they were before. One of the SQL bits I sent you "upgraded" the new blog to use the same settings you had before - except now it comes with a trailing slash.

$baseurl = 'http://localhost/b2evolution/blogs/';

Understood. $baseurl has had the trailing slash since the beginning of the 1.* generation, but the issue is not the $baseurl.

In this case $baseurl is "http://nelsonguirado.com/" but the problem is the slash at the end of $baseurl/index.php/cubanocast/ or $baseurl/index.php/asymmetric/ and so on and so forth. That'd be blog-specific URLs within the installation and the settings that append the blog name to index.php instead of ?blog=N for example. This is a changed behavior from 1.8.5 too, meaning prior to upgrading blog-specific URLs generated by those settings did not end with a slash.

Unfortunately I've no idea how to change that - and especially how to change it without breaking permalinks.

What is the likelyhood of pagerank recovering from the change? I don't know much about page rank, but if it can change down from a change like that then shouldn't it be able to recover as well? Especially given "content before sidebar" and "many validation errors removed" I would think this ranking system thing would be happier. But since I know nothing about it my thinking on it is rather pointless yah?

Yes and no.
Since trailing is 'index.php?blog=N' it assumes the slash is already there. It doesn't matter if it trails the $baseurl or $baseurl/path/to/something/. Once decided to add the trailing slash to $baseurl, it *must* trail any 'path/to/something/'

The trailing slash *really* isn't anything to do with $baseurl. Personally I have the reverse problem with http://domain.com/post-title/ and http://domain.com/post-title, one of them returns a 404 ... I used to have a hack on the 404 page that did a 301 redirect to the non-trailing slash version, but that doesn't help you.

Something you could do ( assuming you don't add new blogs every second of the day ) is to replicate the bloglist by using the free html widget ;)

¥

Since the old URLs go to the blog with or without the slash, I think I'll leave it as is. It only shows the slash when you go from the blog list.