How many blogs does it take to answer my question about pingbacks? The correct answer is at least four, but three of them were mine and I ultimately answered my own question.
When I installed WordPress 2.5, my pingbacks broke. You may wonder what a pingback is or you may not be interested in the slightest. If you are not interested, this may be the post to skip, unless you enjoy watching a kitty chase her tail for hours and hours and hours before remembering she has one important blog, this one, and two test blogs. Normally I don’t have two test blogs, usually it is just one, however, a few weeks ago I was attempting to help a fellow knitting forum member with her pre-2.5 blog, so I installed the version she was running and before I broke my blog at the 2.5 install, I upgraded the test blog to be sure nothing would break. I failed to take into account my web host breaking the one-click install, lesson learned let me assure you. To attempt to head-off any further problems I set up an identical blog to this main one with the same posts and settings behind the scenes, as well as the same plugins also behind the scenes.
After spending a few hours combing the wordpress.org codex, then the “interwebs” at large, I decided my answer did not lay out there, it lay between my head and my three installs. I say it took at least four blogs to answer the question because wordpress.org is a blog and I found a few individuals attempting to be helpful on their blogs, but didn’t answer my question. I also checked WordPress.com to reassure myself that WordPress 2.5 did indeed know how to handle pingbacks. You may wonder what a pingback is, a pingback appears on my blog in the comment of a post when someone out in the wide “interwebs” writes something and links back to a specific blog post of mine.
Out of pure frustration of nothing to show for an afternoon’s worth of work, I set about digging through my theme’s code, hoping maybe the theme was broken, no such luck. I then decided to open the test blogs. I admit, I forgot about the second blog running a really old version of WordPress until I went looking for the password for the first test blog. That second install turned out to be a huge help to the investigative process. I worked to make both 2.5 versions mirror each other in code and active plugins. My main blog would catch one or two out of six actual pingbacks. The other two blogs found all the pingbacks I sent. Again, a bit stumped, I started to wonder if it was a versioning problem with a plugin, the test blog doesn’t have the newest versions of all the plugins I have installed. I only update them when I am using it to test something. It then occurred to me that I redirect this blog. The install folder is not at the root of my site, nor will it be again. That is part of what broke it the first time and made it more difficult to fix. One-click install from my dearest host likes to install to a completely empty folder, no other files or folders present. So when it broke and I reinstalled it, I was going to have to create a subfolder or delete all my photos, files, etc and start over from scratch. I was already deeply saddened by the loss of my blog and did not wish to lose anymore. WordPress 2.x has a setting that allows users to indicate where the blog source files are located while redirecting traffic to another location. In my case, my install is at http://proefrocks.net/blog/, while until today, you viewed it at http://proefrocks.net. My test blogs were not redirecting traffic like the main blog is/was. Once I change the setting to redirect it, the pingbacks broke there as well. Which was a huge relief. I blame my own troubleshooting skills becoming rusty. Ten months ago, this problem would have been solved in under an hour. I also discovered along the way I could force pingbacks if I consistently put a trackback url into each post. That’s not going to happen. I’m trying to retrain my brain to remember to put tags on my posts, about 50-50 there and I’ve always used categories but again, 75-25 there.
To summarize, you will notice a change in my domain layout. When you visit http://proefrocks.net you will now be greeted with a static (unchanging) page with links to several different areas of the domain, one of which will be this blog. I will probably link to Josh’s blog, my photo gallery and the photo gallery for BWCA (Boundary Waters Canoe Area). The page will be updated as changes dictate.
Still to do, create a custom redirect script. June 13, 2008: I created the .htaccess file at the root directory per apache.org. Luckily for me, my permalink structure is simple, all posts from 2008 appear to be in a folder called 2008 and those from 2007 appear to be in folder called 2007. The simple addition of two lines directing requests for 2008 to now go to blog/2008 and 2007 to go to blog/2007 has rendered all links out there in the “interwebs” valid.
P.S. If you remember to move .htaccess and index.php from root back to the WordPress folder, be sure to edit everything and well, I had to empty .htaccess in the WordPress folder which then broke my entire site. I fiddled for another hour and then remembered that plugins cause 2.5 to become rather unruly. I deactivated my gallery plugin, WPG2, emptied the .htaccess again and reactivated the plugin. Then I allowed WPG2 to reconfigure itself, rewriting good things to the .htaccess file.



Home