nutbuster Posted October 4, 2009 Share Posted October 4, 2009 Someone directed me to this site and boy howdy I had 33 errros just on this one product page...used prestashop cleanup icon on the text editor but how do I fix all the other 22 errors? Is there a module on here to do this...this is all new to me...but I am a fast learner Thanks for your help!http://validator.w3.org/check?uri=http://www.kctrading.net/waterless-cookware/9-waterless-cookware-set-28pc-medium-duty.html&charset;=(detect+automatically)&doctype=Inline&group=0 Link to comment Share on other sites More sharing options...
nutbuster Posted October 5, 2009 Author Share Posted October 5, 2009 Wow, I guess everyone just loads it as is and hopes for the best!I hope not...I've got lots of errors in my site...is there an easy way to repair them via prestashop...not sure how to proceed...really need some good advise on this. There does not seem to be much info here on this subject...thanks!Doug Link to comment Share on other sites More sharing options...
rocky Posted October 5, 2009 Share Posted October 5, 2009 A default install of Prestashop has no XHTML validation errors. These errors must be caused by modules you have installed or extra code you have added yourself to Prestashop. I had a look at the errors and they are caused by writing <br> instead of <br />, forgetting to add alt tags to your images (even just alt="" will validate), writing & instead of & and leaving out some closing HTML tags. You need to go through your code and fix these yourself, then your site will validate. Link to comment Share on other sites More sharing options...
nutbuster Posted October 5, 2009 Author Share Posted October 5, 2009 Rocky to the rescue!How do I track down each dir/file name that needs repaired? I like W3C how it shows in lines but will that program show location? Link to comment Share on other sites More sharing options...
nutbuster Posted October 5, 2009 Author Share Posted October 5, 2009 A default install of Prestashop has no XHTML validation errors. These errors must be caused by modules you have installed or extra code you have added yourself to Prestashop. I had a look at the errors and they are caused by writing <br> instead of <br />, forgetting to add alt tags to your images (even just alt="" will validate), writing & instead of & and leaving out some closing HTML tags. You need to go through your code and fix these yourself, then your site will validate. What am I doing wrong here? alt=<!-- MODULE Block advertising --> <!-- /MODULE Block advertising --> Link to comment Share on other sites More sharing options...
rocky Posted October 5, 2009 Share Posted October 5, 2009 I can't see anything wrong with that code. I just did another validation check on your homepage and I see that you are down to 12 errors now. One of the errors is caused by your stat code. You need to put a /> at the end of the img tag to properly close it. Link to comment Share on other sites More sharing options...
nutbuster Posted October 6, 2009 Author Share Posted October 6, 2009 I'll try that on the counter......Tried replacing the & with &: and refreshing and now I have 14 errors and 2 critical....weird? It shows up in Prestashop editor as saved but not when viewd by W3c...W3c is not showing up as & See the attached pic of both below.This url has two such cases of using & one in both the short and long discription both were replaced with & Am I missing somthing? Using & as it's in one of my keywords that showed up under google keywords search.Update: I redid both and now I have two more errors and two critical errors...man this stinks!As you can see when viewed in prestashop html editor at the top it is correct. Tried saving it and save/stay many times...is there something in prestashop that is perventing it being saved??? Can I go directly to this dir/file and see how it is being saved as? Not sure what it would be located? Link to comment Share on other sites More sharing options...
nutbuster Posted October 6, 2009 Author Share Posted October 6, 2009 I can't see anything wrong with that code. I just did another validation check on your homepage and I see that you are down to 12 errors now. One of the errors is caused by your stat code. You need to put a /> at the end of the img tag to properly close it. can you be a little more persist on where to place />?<!-- Start of StatCounter Code -->[removed]var sc_project=5160973; var sc_invisible=0; var sc_partition=31; var sc_click_stat=1; var sc_security="7017db44"; [removed][removed][removed]class="statcounter">href="http://www.statcounter.com/blogger/"target="_blank">src="http://c.statcounter.com/5160973/0/7017db44/0/"alt="counter on blogger"><!-- End of StatCounter Code --> Link to comment Share on other sites More sharing options...
rocky Posted October 6, 2009 Share Posted October 6, 2009 You are right. I just tried entering an & in a CMS page, then saved it, and it is being stored in the database as &, yet when you edit the page, it is converted back to & again. Perhaps we should report this as a bug?I think your stat code is in the right place.EDIT: Sorry, forgot that script tags are removed. Just search for this code: src="http://c.statcounter.com/5160973/0/7017db44/0/" alt="counter on blogger"> and replace it with: <img class="statcounter" src="http://c.statcounter.com/5160973/0/7017db44/0/" alt="counter on blogger" /> Link to comment Share on other sites More sharing options...
nutbuster Posted October 6, 2009 Author Share Posted October 6, 2009 Rocky, that little change in the counter code knocked out a bunch of errors....down to 8 and 2 nowhttp://validator.w3.org/check?uri=http://www.kctrading.net/waterless-cookware/43-12-element-kitchen-cookware-stainless-steel-14pc.html&charset;=(detect+automatically)&doctype=Inline&group=0I will report that bug as I believe it is one too.Thanks for your help!UPDATE: Reported as bug X Link to comment Share on other sites More sharing options...
nutbuster Posted October 6, 2009 Author Share Posted October 6, 2009 oesxyl posted this on the http://www.codingforums.com : <<Senior Coder Join Date: Dec 2007Posts: 4,211 Thanks: 364Thanked 502 Times in 491 Posts I guess the part you try to fix is generated on the fly using ajax, so you must correct the source of that data not the page. >>>>>Ok, so how do I get to the source....dir/file name? Link to comment Share on other sites More sharing options...
TropischBruin Posted October 6, 2009 Share Posted October 6, 2009 Please adjust the title of this topic to: Problem with W3C validator after adjusting template.Thanks! Link to comment Share on other sites More sharing options...
nutbuster Posted October 6, 2009 Author Share Posted October 6, 2009 Please adjust the title of this topic to: Problem with W3C validator after adjusting template.Thanks! Hey Smileys, so you are relating this to the minor template change? This template just changed some of the colors to blue. Link to comment Share on other sites More sharing options...
TropischBruin Posted October 6, 2009 Share Posted October 6, 2009 Please adjust the title of this topic to: Problem with W3C validator after adjusting template.Thanks! Hey Smileys, so you are relating this to the minor template change? This template just changed some of the colors to blue. Thanks for the title change.Visiting your site I see more then just a color change. Link to comment Share on other sites More sharing options...
nutbuster Posted October 9, 2009 Author Share Posted October 9, 2009 Please adjust the title of this topic to: Problem with W3C validator after adjusting template.Thanks! Hey Smileys, so you are relating this to the minor template change? This template just changed some of the colors to blue. Thanks for the title change.Visiting your site I see more then just a color change. Yes, more than a color change SOLVED:Guess what?!?! I figured it out with a little help from my coder friends http://validator.w3.org/check?uri=http://www.kctrading.net/waterless-cookware/43-12-element-kitchen-cookware-stainless-steel-14pc.html&charset;=(detect+automatically)&doctype=Inline&ss=1&outline=1&group=1&No200=1&verbose=1&st=1&user;-agent=W3C_Validator/1.654Diffrent brackets were throwing off the search as they were diffrent in W3C compared to what was actual used in the file on my web server as I found it in a diffrent DIR Prestashop and not etcleanblue templete area but was able to reword search and trace the defect in product.tbl under etcleanblue dir Man that felt good to find this! File that needed changed:/public_html/themes/etcleanblue/product.tplThis missing alt tag could of been from installing the on sale module? Not sure if there is a bug in that module? But adding the text below will fix that nasty W3C error Go here for more info as the code I paste is now showing up on this forum See post #23http://www.codingforums.com/showthread.php?t=179003&page=2 Link to comment Share on other sites More sharing options...
Recommended Posts