What Does Your Site Look Like On All Browsers?

Last week while I was over a friend’s house, I wanted to show him my local Syracuse blog. He uses Internet Explorer (seems there’s still a lot of those out here lol) so I pulled up the main page and all looked fine. Then I pulled up an individual post and… ugliness!


bad code

I forgot about it until I was reading a post on a blog called IBlog4Dollars titled 35 Serious Blog Design Mistakes That You Should Avoid At All Costs written by Dennis Marshall. I got to #10, where it talked about making sure your website is cross-browser compatible, and then I remembered the problem I was having with IE.

I pulled it up on my IE and I had the issue like my friend did. I then went to work, and for the next 4+ hours I went through all the CSS code and checked all the PHP files, looking for something. I ran it through the W3C CSS Validator, which found some errors but nothing causing the issue. Man, was I frustrated.

Luckily, I play chess with Mitch Allen, so I threw the question out to him via one of my chess moves. He came back with a diagnosis that it was some javascript in the code, probably the Google Analytics script.

As I’d been researching the issue, I had come across something where it had been predicted that javascript could cause issues, but it never occurred to me it could be that one.

I went to the theme and then had to search for where I’d put it. Most of the time Google Analytics script works best in either the header or footer, but I realized I’d put it somewhere else, and then I remembered why. For some reason I can’t save many of the files on this particular theme. I get sent to a 404 page after attempting to do so, which was irksome. I found the script in a PHP I’d never put it on anywhere else because it turned out to be one of only 2 files I could actually save.

Once I removed it the site came back to life for IE8, which was great, but I still had a problem; how to get that Google Analytics code in. After all, if I couldn’t track my traffic, I wouldn’t know how I was progressing or digressing right?


good code

Then I remembered that sometimes you can fix things through your FTP program. I use something called WS_FTP for that purpose, so I opened that up, went to the plugin file and clicked once on Header.PHP. Then I right-clicked and went to Edit, and I popped the code in and saved it.

Came back to both my Firefox browser and IE, ran my tests, and all is working perfectly still. Just to make sure I also tested it in Chrome and Opera; looks good so far. Whew!

You can pick up things from other blogs, that’s for sure; heck, even this one I suppose. I had obviously taken time to see what that blog looked like before, but only the main page; that was a mistake, one I need to remember not to do again. One little code; with IE, sometimes that’s all it takes to mess stuff up.
 

Digiprove sealCopyright secured by Digiprove © 2012 Mitch Mitchell

Internal Server Errors And Plugins

I’ve been having all sorts of issues with my dashboards ever since WordPress 2.8 came about. I also kept having Internal Server Error 500 pop up from time to time. With 2.8, I actually found a fix for it, and that should have been that.

But with each update, that fix wasn’t working so much. None of my blogs worked well after 2.8 anyway, and we had to keep updating. And the WordPress people kept updating every two weeks, and that was irritating because automatic upgrade wouldn’t work for me. When WordPress 2.8.4 came out, I decided I wasn’t upgrading at all; nope, just wasn’t doing it.

That is, until I started reading all the news about blogs that hadn’t updated being hacked into and basically having all content destroyed. Man, nothing will get you moving faster than scary news like that. So, I finally updated all my blogs; one had already been updated when I was hoping to fix something else, but it hadn’t fixed my issue.

Over the last couple of days I’ve been getting that Internal Server Error thing over and over, and never when doing the same thing. I was going nuts, and I was trying to check plugins and even thought about reloading my software. And I was right on the verge of doing that when I decided, based on research, that it had to be the plugins, or at least some of them.

I started with my business blog, which was having the most issues. I turned off all plugins except Akismet. Then I went to the dashboard; it was working perfectly. Slowly and surely, I added one plugin at a time, to see which one would make the dashboard stop working. I was hoping it was only one, and I was hoping it would be WP Super Cache, which I’d just loaded.

Turns out it was WP Super Cache; but it wasn’t alone.I had to kill four other plugins as well. Those were Broken Link Checker, Gravatar, Why Do Work Adsense, and WP Ajax Edit Comments. I couldn’t believe it was all of them, but there it was. The only one that’s really bothering me a lot is Broker Link Checker, because it works great. The others,… well, I’d like to have them, but I really don’t need them.

I turned on WP Super Cache because my blog had been running a little sluggish, and I thought that would take care of it. Turns out it didn’t do anything, as there was another plugin that was recommended to use with it, but it wouldn’t work on my blogs because, supposedly, my host is running PHP version 4 instead of version 5. I might not have the terminology fully correct, but I have the essence and the numbers correct. Anyway, it didn’t work on this blog, so it doesn’t really matter that I’m removing it, for the second time.

I then went to my finance blog and deactivated the same plugins, if I had them there, and went to the dashboard. There was still a problem. I had a feeling I knew what the problem was, and I was correct; my plugin called Backup WP was the problem. It’s the only blog I had it on, as I use WordPress Database Backup on the other blogs, so I’ll just switch to that and things will be just fine.

Then I came to this blog and did the same thing, and there you are; all is right with the world once more. Now, what I want to make sure I say is that I don’t know that one of these plugins may work well on its own, but doesn’t play well with another plugin that I loaded first. However, I loaded the plugins I really felt I needed first, and if they worked, then I moved on to the next one.

Anyway, now I’ll monitor things over the next few days to see if I get that error again. I hope not; this can be quite tiring. Check out your plugins if you have any problems. Deactivate them all first if you need to, like I did the first time around, and if you have no problems after that, you definitely know it’s a plugin issue. Good luck,

Woo Pom Pom Scarf

Woo Pom Pom Scarf






Digiprove sealCopyright secured by Digiprove © 2010 Mitch Mitchell