![]() ![]() Let’s start eliminating things that we know are NOT causing the problem. Using the web inspector of your choice (we’ll use Firebug for Firebox), look at your source code. ![]() Here’s an example of the basic Genesis Website structure: What if the issue is both in the header AND footer? There’s just too many variables and troubleshooting this way is very challenging, time consuming and frustrating. You’ll probably lose track of what you tested. It’s too much code to go through manually. If you start looking through your code, going through the header, line by line, next the title-area, logo, widget area, and on and on what’s going to happen? Using the example above, it’s obvious that something is too wide, causing the horizontal scroll bars to appear. ![]() You have to narrow down the issue, and to do that you have to eliminate the things you know are not related to this issue. Instead of trying to fix the issue right away, let’s eliminate the things for certain that are NOT related to the issue. Troubleshooting The Right WayĪ better approach is to use the Process Of Elimination. Many of the support requests include ‘I’ve been working on this all day and I can’t figure it out.’ Why? Because there’s a million things going on in your website code, and you’re trying to fix the problem without knowing where it is. Most people will dive into the code, line by line trying to figure out what’s causing the problem. After the screen size is reduced something is not adjusting right and it’s causing the page to be too wide, resulting in a horizontal scroll bar. Something’s causing a horizontal scroll bar to appear and ‘I can’t figure it out.’ Usually it happens with responsive sites (although it can happen with any site). I’ll use an example that comes up fairly often on the StudioPress Genesis Forums. When someone is troubleshooting an issue, most people immediately focus on fixing the problem. (The code examples in this article are specific to the Genesis Framework by StudioPress, for WordPress, but they can be applied to any website.) Troubleshooting The Wrong Way If you can master troubleshooting, you’ll significantly cut down on your overall development time, as well as the amount of time it takes to handle any issues that come up. It’s a great way to learn and it’s a great way to speed up your workflow. I love the challenge of figuring out an issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |