As part of providing support, I often get an inside look at WordPress conflicts. If you’re troubleshooting your own site a great step is to disable all of your plugins and see if that fixes your problem. If it does, then you just need to reactivate your plugins one at a time until you discover the conflict. That’s tried and true WordPress advice. But what do you do if you don’t have access to the WordPress control panel? Here is a quick method I use to solve conflicts on other people’s sites.
Thanks to WordPress using absolute links for everything, you now a local copy of the code that WordPress produces. If you open this index.html file in a web browser you will see a copy of your site (complete with the conflict). Now that you have a local copy you can begin to trouble shoot. Next you will need to look for tags where plugins and the theme load scripts. These generally will be at the top and bottom of the page. Many plugins place a note saying where their code starts and ends which is helpful in hunting out the conflict. Here’s how I treat these items that are loaded:
That’s it. Now you know a way to help deduce conflicts in other people’s sites without needing to access their WordPress back end.
Maurintius said:
on March 31, 2011 at 3:59 pm
Did you ever came across the fact that when you see or other people see the homepage, you can keep scrolling down and, where the page normally stops, it goes on and you see all the code from the posts you posted?
Thanks in advance for the help.
grzt
Bill Robbins said:
on April 1, 2011 at 2:06 pm
I can’t say I’ve ever run across that one. Can you give us an example?