Although Facebook Comments launched in 2011 it wasn’t until recently that I decided to implement the comment system into my blog. There were several reasons why I didn’t pull the trigger on the new comment system when it launched, but the primary reason was simply because there was no out-of-the-box method to export all the comments from my then-comment system to Facebook Comments. However, after kicking around the pros and cons for a bit, I took the plunge and installed Facebook Comments since it will reduce the number of trolls, silence the anonymous commenters, and help facilitate higher quality conversations. That being said, here’s to a fresh start!
Okay, so in this tutorial I’m going to explain how to manually implement Facebook Comments for those of you who choose not to install a plugin or unable to install a plugin due to an old WordPress version you might be running. Let’s get started.
The other day one of my colleagues was trying to add a hyperlink to our company logo so when someone clicks on the image it will redirect them to our company website. Unfortunately his attempt was unsuccessful so he reached out to me for assistance since he noticed that the logo in my signature was already linked. Normally IT or marketing departments handle this task, but because we’re a tech startup we must wear multiple hats around here and sort these things out ourselves. That being said, after negotiating a delicious lunch in exchange for my services I walked him through the steps. I kid. I kid. I didn’t charge him anything for the help. Okay, moving on…
Although adding an image to a Gmail signature is fairly simple, linking the image to a website appears to be a difficult task for a lot of people. Therefore, I thought it would be a good idea to publish a tutorial that explains how to accomplish this task. Here are the steps to convert your logo into a hyperlink image:
A buddy of mine left his WordPress blog unattended for several months because he wasn’t publishing new content at the time nor was he monitoring the comments. Unfortunately, his blog didn’t have a Disqus or Facebook comment system in place and he failed to include a spam filter such as Akismet with his current comment system. The result: thousands and thousands of spam comments flooded his blog posts.
At the time of this writing, WordPress doesn’t have a way for the user to send spam comments to the trash with a single click. I’m sure that feature will be added in the future, perhaps an “Empty Spam” button similar to the “Empty Trash” button, but for now the user must either manually select each spam comment and send it to the trash or install a plugin that will do the trick. Clearly the former option isn’t going to work well for anyone and sometimes installing a plugin reduces the speed of the WordPress blog.
While there are several tutorials on the Internet that explain how to install PHP on Windows Home Server (WHS) / IIS 6.0, I noticed that many of these tutorials are not precise and some even miss important steps in the process that could benefit the average user. Those who know their way around IIS and have basic knowledge of editing code would not have any trouble following the instructions that are currently out there in “www World.” However, a good portion of WHS users, especially HP WHS users, are not advanced users and need a step-by-step guide that will allow them to install PHP without jumping through hoops and over hurdles. I’m not trying to reinvent the wheel or waste the *online-ink* by writing yet another tutorial on this topic, but I feel it is necessary to cover every step in the process so the installation is flawless. I am going to cover the steps that I believe are the most efficient so we can knock this out.
It is extremely important that each step in the installation process is followed exactly as outlined below. If you read everything carefully you will have PHP running in no time. Although the installation process seems lengthy, it will not take too much time once you get the ball rolling. I went a bit overboard when writing this tutorial, but I rather be thorough so everyone has a shot at a successful installation opposed to cutting corners in my tutorial and leaving people hanging.
Soon after I installed WordPress on my Windows Home Server (WHS) which runs IIS I realized my permalink options were limited since IIS does not support mod_rewrite. I definitely wanted to produce Pretty Permalinks, therefore, I spent some time searching plausible solutions that would mimic mod_rewrite capabilities so I could accomplish this goal. What I found were several workaround tutorials that explained how to create 404 redirects while others provided instructions on how to use PHP and INI files in association with a ISAPI Rewrite Filter. Nonetheless, I was not interested in going through all the tedious steps in these workarounds so I continued doing my homework. Thanks to a project on Google Code I was able to find a solution that works perfectly and only takes minutes to implement.
Before I take you through the steps let me back up a minute for those of you who are not familiar with Pretty Permalinks. Permalinks are the permanent URLs to individual blog posts, as well as archives, categories, and other blog postings. According to WordPress, “Pretty Permalinks is the idea that URLs are frequently visible to the people who click them, and should therefore be crafted in such a way that they make sense, and not be filled with incomprehensible parameters.” For example, if you choose the permalink “Month and Name” option it would produce a URL that would look like this:
When I embedded reCAPTCHA into my WordPress blog the first thing I noticed was that reCAPTCHA was sitting directly on top of the “Submit Comment” button without allowing any breathing room between the two. The appearance was rather obtrusive so I decided to do a quick search for a solution using my buddy, “Google.” Normally I would muck around with the code myself and call it a day, but I figured there was someone who already found a fix and shared it with the rest of us. As it turns out, there are many forum discussions about this same exact issue and several on the WordPress forum, yet no solutions were ever posted.
So, after wasting a few minutes searching for a solution, I decided to look through the code so I could figure out how reCAPTCHA was embedded into the comment section of the blog and attempt to correct its placement. My first instinct was to add a simple “break (
<br/>)” tag in the comments.php file, above the “Submit Comment” button code, so this way it would add some space. However, this edit was unsuccessful and I quickly realized the only way to make this work was by combing the reCAPTCHA PHP file and looking for the correct section in the code to add a “
<br/>” tag. After I opened the reCAPTCHA PHP file it did not take more than a minute to figure out which section needed the “