After being frustrated with mod_rewrite mojo, I wrote a quickie no-www plugin for WordPress that redirects people to the non-www version of your URLs, in the spirit of no-www.org. ¶
Good stuff Matt. Is there a way I can reverse this and have everyone coming from http://domain.com redirect to http://www.domain.com
thank you!
I’m using this now and it works perfectly!
All I had to do was activate it.
That’s it!
It rocks!
I love easy plug-ins like that!
Thanks!
Heh, DreamHost has a neat little util in the panel that lets you do exactly that. I’m proud to say I’ve been no-www for quite some time now!
Good idea to write a plugin though. I don’t think people realize how much of a hit they take in search engine ranking when they allow both www and no-www. Check out digg’s ranking vs. slashdot on http://populicio.us/fulltotal.html. Digg’s combined numbers easily beat out slashdot, but because its numbers are split due to www and no-www, it sits at 6th and 11th.
Awesome! I’ve had the mod_rewrite rule in my .htaccess for a couple months. I just installed the plugin and erased the mod_rewrite rule. Everything works flawlessly.
I’ve been experimenting with a different approach: root-relative WordPress addresses.
The one downside I’ve found so far, and it’s minor, is that my RSS feed reader (Akregator) breaks the UA rules and doesn’t prepend the scheme/host to the relative URLs that now appear in the feed. I suppose I could force absolute URLs in the feed using a plugin.
Does this do the same as the plug-in called Objection redirection? Found here; http://wordpress-plugins.biggnuts.com/objection-redirection-wordpress-plugin/
I have downloaded this plug-in, but haven’t activated it yet because I found your new plug-in. Obviously I would go with yours over someone else any day.
PS- could you also shed some light on this whole meta tag issue I’ve been reading on the net. The way I figure it, you are expert at all things WordPress; so if meta tags were a necessity, you would have built it all into WordPress to begin with.
Thanks!
Yep it looks exactly the same as those other plugins, except a little more bare. I should Google more! 
ummm… if DNS is setup properly, you don’t have to use w3 anyway… w3 is not “required”.
man, I thought it was just me who didn’t like the http://www….
Methinks your plugin doth fail too much. Any link on your site I try to load that doesn’t have the www gives me a very silly 404 error.
Um…
http://photomatt.net/2006/06/13/wordpress-no-www/
404 Not Found
The resource requested could not be found on this server!
Have you turned the plugin off? It doesn’t appear to be working on here!
http://www.photomatt.net/2006/06/13/wordpress-no-www/ gets to this page just fine but…
http://photomatt.net/2006/06/13/wordpress-no-www/ give a 404
Don’t know if it is temporary, but at 19:47 BST (GMT+1) I get this:
http://photomatt.net/2006/06/13/wordpress-no-www/ = 404 not found
Hey sorry guys, my site is messed up for another reason. When the password thing happened my site somehow got delisted from Google without the www, so I’ve been experimenting with changes to bring it back.
awesome! i have struggled with the www vs non-www issue for awhile.
Hot Dang! Just was I was trying to (unsucessfully) pull off via .htaccess last night. Thanks Matt! You ‘da man.
I wrote a plugin that does it both ways… that is, it enforces your yes-www or no-www preference as set in Options » General.
Enforce http://www. Preference
Arggg….
http://www.whalesalad.com/2006/06/07/whats-up-with-these-urls/
Nice plugin..
But after I activated this plugin I noticed one problem.
If I try to setup my blog via a weblog client say Flock or Qumana, I am getting a error while providing the authentication information(User Name/Password) The HTTP status code is 301.
Even I tried to post a new blog from the already configured client and I was getting the same HTTP status.
I deactivated the No-WWW plugin and everything was working fine !!!
Probably you need to check on this.
Ooops ! I guess I gave a feedback too soon.
When registering the blog in the web log client if I give a “No-www” url its working fine
Appears this error:
It needs to qualify the send of referrers so that this works.
(Necesita habilitar el envÃo de referrers para que esto funcione.)
I close all windows, and star again and works, strange, do you?
Regards!
@
Arrrgggghhh, indeed.
Installed fine. (Except for a false error from WP “Sorry, you need to enable sending referrers for this feature to work.” Got the same error in two different browsers that have “sending referers” enabled.
But… checked back and the plugin reported itself installed and the no-www.org site reported my blog as a “Class B” compliant site.
Then, I becgan getting emails that my wp-comments-post.php page would not display. Yup. No comments. This plugin was the only change, so… went to deactivate it and… “Sorry, you need to enable sending referrers for this feature to work.” And this time, no deactivation.
Guess I have to nuke the thing via ftp and seek a plugin (or other method) that’ll work w/o hashing things up. Nice idea. Works fine except for the comments issue and the weird “Sorry, you need to enable sending referrers for this feature to work,” error that cropped up for the very first time after installing this plugin.
Yep. Just nuked the plugin via FTP and both issues are gone.
That plugin is fantastic I just now need to get round to migrating away from Movable Type over to WordPress at somestage in the future.
If you’re having problems, make user you change your URL under Options > General to not have a http://www.
Whoah…
It’s doing the opposite for me.
http://neosmart.net/blog/ goes to http://www.neosmart.net/blog/
And in my options page there is no http://www.
Maybe it has to do with my blog being in a subdomain?
I had no issues with Mark’s plugin, I’m only using this one because it’s lighter on the server.
Oops! I meant on a subfolder - not subdomain.
While this plugin and other like it will indeed work, I really recommend using the .htaccess method instead, if you can get it to work.
It’s actually very simple to do. Go to http://no-www.org and scroll down the page until you find the post titled “Make your site Class B”. Copy that htaccess code into the .htaccess file at the root of your webpage. Change the “domain” to your own, obviously.
Done and done.
This plugin, while useful, needs to use implode() on $_GET in order to pass query string variables such as, I don’t know, s=
btw in my comment #2 I mentioned how to reverse this. You can find a new great plugin by Justin at:
http://www.justinshattuck.com/wordpress-www-redirect-plugin/
I implemented the plug-in on two sites (one running WP2.0.1, the other 2.0.3) using two different (but fully working) themes, and I found that comments got broken on both sites, leading to a blank page of wp-comments-post.php. Deactivating the plug-in fixed comments immediately. Both sites were running php 4.4.2 if that might have an effect…
Matt, you’re the man! I’ve been trying to figure out how to make this work for a few weeks. My host wouldn’t work with most of the options. This way works great. Thanks much.
Rob | June 13th, 2006 @ 3:33 am
Hi Matt,
Thanks for wrapping this into a plugin. I’d implemented the no-www Apache script to solve a host of Ajax issues with my Wordpress install but it’s good to have a solution that works with WP’s existing .htaccess editing