Click to Play PayPal's New Toolkit for Google... PayPal made some cloud computing advancements at Google I/O by announcing its X Toolkit for Google App Engine (GAE). WebProNews spoke... Recent Articles How To View And Edit Your Whois Data To Increase SEO This is only one SEO tip out of many search engine optimization tips I have been providing over the years. All of my search engine optimization tips are meant to be specific, they should not take too much time... Adding Extra Social Media Connections With... I've been inspired by your Facebook fan page, Dave, and have one of my own. Now that I have it, though, I'd like to be able to inclue a "like" box on my blog so that people not only see a link to the fan page... Adjusting Your Live Website Using Webmaster... OK, so you've got your site set-up and configured in Google Webmaster tools. Now it's time to start looking at the data. Your Site on the Web. Google Webmaster Tools allows you to view some basic stats and... How To Initially Set Up Your Website hAll right beginners pay attention and I'll instruct you "How To Set Up A Web Page Free"!!! There are a lot of sites out there that make you believe that they are going to give you free website or free web addresses or free something or the other. What you don't...

How would you go about debugging this one?

My immediate thought was to blame a plugin. Why? Because WordPress's great coding strength is also its weakness - hooks and filters give plugin authors the ability to mess with the output of "core" WordPress functions. But it's really hard to tell if any messing around is going on, in order to debug problems.

Question then: how do you figure out if one or more plugins is using a hook/filter to mess with the output of a given WordPress function?

If you have shell access to your WordPress host I've got a little treasure for you today. A simple enough shell command that will make your life a lot easier. (If you're a "real" programmer you'll almost certainly know about this already, but if you're not, you're gonna love it!)

Now, shell access (SSH) gives you "command-line" control of the operating system on which your WordPress blog resides. If your hosting provider has given that to you and you know how to use it, you can do cool stuff like ZIP up all the content in one hit so you can back it up really easily, say. Lots of fun to be had.

Today I want to show you how to return search results for all the instances where a certain string appears in your plugins' PHP files. That's how we're going to debug my problem with the the_excerpt() function today.

Here's the command to run at your SSH prompt when you've navigated into your wp-content/plugins directory:

find . -name \*.php -exec grep mystringhere {} +

(Note that on older systems that last plus sign might need to be replaced with a semicolon ";".)

That command simply isolates all php files and searches through each in turn for each occurrence of "mystringhere". For each occurrence it finds, it shows you that line of code preceded by the filename and line number. Easy!

Because I don't like the black and white of my Terminal application, I then copy out all the results found into my code editor, so that I get to see the code in all the pretty colours that Coda puts it in. That's up to you.

For purposes of example, here are the results I got from my client's plugin directory(pops up a new window).

Yes it looks like a huge mess, but you can see now that it's really easy for me, in my code editor, to search through all that for "add_filter" and "add_action", to see where any plugin is messing with the output of the the_excerpt() function.