Comments on: Watch Out – Canonical URL Bloopers

By: Terry

Terry — Tue, 04 Oct 2005 23:58:02 +0000

Dani wp seems to handle it fine. No errors showing up in the stats, plus I’ve been pulling the blog feed with carp (showing on the directory). Everything’s running smooth.

I also double checked with Google, Yahoo and MSN and the pages they’ve spidered – no errrors with those pages:

http://www.google.ca/search?hl=en&q=site%3Afabaroo.com%2Farticles%2F&meta=

Thanks for that head’s up, something to definitely watch for with other blog software.

By: Dani

Dani — Tue, 04 Oct 2005 18:15:57 +0000

Beware, there’s some software out there that won’t allow you to fix this problam. Or at least, in combination.

I have a directory script in a subfolder that uses virtual directories. In the main folder is a blog. With my current blogging software, it won’t do the WWW redirect without breaking its other rewrite rules that create the virtual directories. I THINK when I had WordPress, this wasn’t true, but I’m not sure. I think late one night, I’ll have to install WordPress over what I already have (backing up my current setup) and see if it works. If so, I may have to go back to it.

At this point, I’m not sure whether it’s the blog’s rewrite rules that are funky or the directory.

Next time, I’ll test my setups better before I commit to a particular script.

By: Terry

Terry — Mon, 03 Oct 2005 13:05:20 +0000

Jon I’m not an .htaccess wizard by any means, but this is what I did for fabaroo’s article blog:

http://fabaroo·com/articles/$1

Now when I try to access http://www.fabaroo.com/articles/ , it directs to fabaroo.com/articles/ so I’m thinking it works

By: Jon M

Jon M — Mon, 03 Oct 2005 11:34:43 +0000

How do you make changes to the code?

By: mpeters

mpeters — Mon, 03 Oct 2005 04:25:07 +0000

Thank you for this warning. I checked and six of my sites are having problems in the sub folders. Mainly for blogs (all wordpress). I added the code to .htaccess in those folders like you said and its fine now. Only one site I can see was targetted by sites linking to the wrong version so I was lucky.