Please help! Looks OK in Firefox, Not OK in I.E. ?!

myemmadoodle:

I'm still wondering about the logowrapper section... should I still put the image url into the logo wrapper rather than where I currently have it? :blush:

It wouldn't have been necessary to remove height:75px; from #logoWrapper if the header image were correctly coded.

RescoCCC:

It wouldn't have been necessary to remove height:75px; from #logoWrapper if the header image were correctly coded.

Wow. Um. If I knew what I did wrong in adding the header in the first place, and knew how to fix it, I would, trust me. I don't know how to fix any of the errors on the validation site because I don't know where everything is located (which files to edit etc). Unless you can tell me how to correctly code it and which files to edit, then shush, you're just being mean now. :yuck:

I give up.

RescoCCC:

I give up.

Probably for the best. I said in a previous post that I tried to put my image url into the logowrapper area where it was blank and where you said it was supposed to be, and remove it from the page area where you said it shouldn't be, and my whole header disappeared (well the page kinda moved UP in front of the header actually, it was screwy for sure) in I.E. so I panicked and put everything back to where it was, just removing the height:75 px and everything now appears normal. There are a lot of errors on the validation site that are just plain silly like my title of "Bundle & Save", the & symbol gave an error?! Pft. :ohmy::shocking:

Most of your validation errors are unescaped ampersands. Any time you hard code an ampersand (&) in a website, you need to 'escape' it by adding amp; so it looks like this: &.

Fix those and most of your errors will go away.

stevesh:

Most of your validation errors are unescaped ampersands. Any time you hard code an ampersand (&) in a website, you need to 'escape' it by adding amp; so it looks like this: &.

Fix those and most of your errors will go away.

It doesn't actually EFFECT my site though? From what I can tell, people can still browse, purchase, download etc and not really be effected by the & symbol... eh? That's just kinda nit picky type stuff, yeah?:huh:

It's nit picky if you don't need traffic from Google or other search engines, I guess. Since it wouldn't take that long to fix, I'd go ahead and do it.

stevesh:

It's nit picky if you don't need traffic from Google or other search engines, I guess. Since it wouldn't take that long to fix, I'd go ahead and do it.

Other than my Bundle & Save area, which I just fixed, I'm not sure where else I have to go to fix the & symbols that are throwing errors... I just don't understand, half of the errors on the validation site are errors in the coding that I've gotten from other places and were told to copy and paste into my coding, so it's like it's THEIR errors and shitty coding, you know what I mean? Like with the Paypal Seal coding, and even some of the zen coding that is already in the template or my product listings etc ... I know my header coding is still not proper, but everything seems to be working alright and looking okay, and some of the errors the site is throwing off are just too complicated for me to figure out! I will try and be more careful when it comes to the & symbol though, thank you for explaining about that! :blush:

They may be their errors, but it's your SEO that will suffer if you don't fix them. (Another option would not to use their code on your pages.)

Taking another look at your site in the validator, it seems that a lot more of your errors are images that don't have alt tags, like this one:

<img src="http: //i281.photobucket.com/albums/kk221/PimpMyTagsWithScraps/pmtws_host-label.png" alt=''host-label" >

Adding the red part will make that error go away.

One tip - if you open your site in Internet Explorer or Chrome and veiw the page source, you'll have line numbers which pretty much match the line numbers the validator is referencing, so you can just go to that line in the source to see where the problem is.

stevesh:

They may be their errors, but it's your SEO that will suffer if you don't fix them. (Another option would not to use their code on your pages.)

Taking another look at your site in the validator, it seems that a lot more of your errors are images that don't have alt tags, like this one:

<img src="http: //i281.photobucket.com/albums/kk221/PimpMyTagsWithScraps/pmtws_host-label.png" alt=''host-label" >

Adding the red part will make that error go away.

One tip - if you open your site in Internet Explorer or Chrome and veiw the page source, you'll have line numbers which pretty much match the line numbers the validator is referencing, so you can just go to that line in the source to see where the problem is.

Thank you for the advice... I sincerely appreciate it. Problem with going through them all is that I have a hard time remembering where every file and image is located at... like which file to pull from FTP and fix and where it's located. All the errors are in different files all over the place in ftp right? It's not like it's just one file I grab, make all the changes in that file and re-upload it... if it were THAT easy, it would have been done a long time ago! LOL! :blush::blink: ...by the way your help is amazing. You explain everything just like I'm a total newb (which I am) and I completely understand you! I know for some people that is super hard to do, with them being used to talking to pro's and geeks, but with me, I know just enough to get by, but you're teaching me a ton! again... Thanks!:hug:

This feels like the time I gave the homeless guy a $20 GC to Mickey D's. He chewed me out for not giving him money.:wacko:

Your site is presenting gibberish to the browser. As I stated, your initial HTML declaration is extremely flawed. It's like giving you a piece of paper with words on it and expecting you to translate it without a clue as to what language is used on the paper. Firefox is one of the smartest browsers and will look at the overall picture to make assumptions about the "language" (HTML) and translate it to the user's screen. IE is probably the bottom of the list as they want you to code their way versus W3C standards. There is a lot of code inherent in ZC just to make it play well with IE. We would all be better off if IE were discontinued.

BUT....there is still the problem of SEO. A lot of the search engines are just as dumb as IE OR, they don't want to take the time to figure out what your code is trying to say. So, if you don't care about the Search Engines getting an accurate look at your site, you can stop reading here.

Out of the box, ZC 1.3.9h had one validation error but only if you didn't use the easypages header. It displayed an extra <li> tag that was easily ignored by browsers and search engines alike. Can't say for sure yet about 1.5, but I know it does not present gibberish that IE can not handle.

As to code you've added from friends and add-ons... I'm one of the first to say we need better evaluations before add-ons are presented to the ZC community. However, the time and expertise to do that would be enormous. Each add-on should be researched before jumping in with both feet. I'm amazed that folks will just throw something in a live site without even looking at the support thread. Would anyone do that to their car?

As to the busy chick comment. In 2003, I was researching for ideas in creating my own store. I had spent twenty years teaching myself code and was currently working with ColdFusion. I felt I could incorporate things I found into my own version that would fit my needs. During that research, I found Ajeh when she was with OSC. Having the heart of a teacher, Linda quickly helped me see that I could spend countless hours inventing the wheel or a few days making something work for me. I had never coded in PHP but had dealt with databases. Within a year, Linda moved to Zen Cart and I moved as well. Whenever I had a problem, she was quick to respond. Not always with an answer, but always pointing me in the right direction. I call it help versus a handout.

Today, I host, code, design, and help (when accepted) while maintaining two other businesses and making sure I attend all the scheduled events for five grandkids. While doing that, I try to be on this forum helping those who are here to learn. I specifically point folks to places they can learn. If they want a handout, they can pay for my services. If they want to learn, I'm just passing on what Linda did for me.

In my post for you, I didn't take the time to point out each fix but did send you directly to what I think is the biggest problem you have. That is the incorrect declaration of the HTML. Your code has> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">While still not quite correct, changing it to > <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">will at least get rid of the duplication.

Standard for ZC is> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en">Hence the facebook comment. Both items in the declaration should be in the META area to work better.

Since my post, the number of errors on your site have increased but the warnings have gone down. Unfortunately, the errors are the gibberish that needs to go.

Can't say for sure where this was changed in your site as we don't know how you or your friend changed it. It SHOULD be changed in either the english.php file or a custom english.php file around line 45.> // Global entries for the <html> tag

define('HTML_PARAMS','dir="ltr" lang="en"');If your english.php file does not have the facebook and opengraphprotocol items, then you will need to use the developer's toolkit to find where they are in your site. Many will try to hard-code the parameters rather than find out how to really change them. We cannot see into your files to find out if this change was done "by the book" or not.

Lastly, a quote for one of your scrapbooks.> Don't bite the hand that feeds you.

Have a great New Year.

dbltoe:

This feels like the time I gave the homeless guy a $20 GC to Mickey D's. He chewed me out for not giving him money.:wacko:

Your site is presenting gibberish to the browser. As I stated, your initial HTML declaration is extremely flawed. It's like giving you a piece of paper with words on it and expecting you to translate it without a clue as to what language is used on the paper. Firefox is one of the smartest browsers and will look at the overall picture to make assumptions about the "language" (HTML) and translate it to the user's screen. IE is probably the bottom of the list as they want you to code their way versus W3C standards. There is a lot of code inherent in ZC just to make it play well with IE. We would all be better off if IE were discontinued.

BUT....there is still the problem of SEO. A lot of the search engines are just as dumb as IE OR, they don't want to take the time to figure out what your code is trying to say. So, if you don't care about the Search Engines getting an accurate look at your site, you can stop reading here.

Out of the box, ZC 1.3.9h had one validation error but only if you didn't use the easypages header. It displayed an extra <li> tag that was easily ignored by browsers and search engines alike. Can't say for sure yet about 1.5, but I know it does not present gibberish that IE can not handle.

As to code you've added from friends and add-ons... I'm one of the first to say we need better evaluations before add-ons are presented to the ZC community. However, the time and expertise to do that would be enormous. Each add-on should be researched before jumping in with both feet. I'm amazed that folks will just throw something in a live site without even looking at the support thread. Would anyone do that to their car?

As to the busy chick comment. In 2003, I was researching for ideas in creating my own store. I had spent twenty years teaching myself code and was currently working with ColdFusion. I felt I could incorporate things I found into my own version that would fit my needs. During that research, I found Ajeh when she was with OSC. Having the heart of a teacher, Linda quickly helped me see that I could spend countless hours inventing the wheel or a few days making something work for me. I had never coded in PHP but had dealt with databases. Within a year, Linda moved to Zen Cart and I moved as well. Whenever I had a problem, she was quick to respond. Not always with an answer, but always pointing me in the right direction. I call it help versus a handout.

Today, I host, code, design, and help (when accepted) while maintaining two other businesses and making sure I attend all the scheduled events for five grandkids. While doing that, I try to be on this forum helping those who are here to learn. I specifically point folks to places they can learn. If they want a handout, they can pay for my services. If they want to learn, I'm just passing on what Linda did for me.

In my post for you, I didn't take the time to point out each fix but did send you directly to what I think is the biggest problem you have. That is the incorrect declaration of the HTML. Your code hasWhile still not quite correct, changing it to will at least get rid of the duplication.

Standard for ZC isHence the facebook comment. Both items in the declaration should be in the META area to work better.

Since my post, the number of errors on your site have increased but the warnings have gone down. Unfortunately, the errors are the gibberish that needs to go.

Can't say for sure where this was changed in your site as we don't know how you or your friend changed it. It SHOULD be changed in either the english.php file or a custom english.php file around line 45.If your english.php file does not have the facebook and opengraphprotocol items, then you will need to use the developer's toolkit to find where they are in your site. Many will try to hard-code the parameters rather than find out how to really change them. We cannot see into your files to find out if this change was done "by the book" or not.

Lastly, a quote for one of your scrapbooks.

Have a great New Year.

I thank you for taking the time it took to type that all out. It does help me understand things better. You are one of the lucky few that had someone take you under their wing while you were learning and guide you through it all... not all of us are as lucky! Again, thank you for your time. :blush:

Had my wing not been bitten off............:P

dbltoe:

Had my wing not been bitten off............:P

snort :laugh: At least you HAD wings once! :lookaroun:wink: