my esport site virtue mart site distorted

GK User
Fri Sep 20, 2013 7:05 am
Hi my esport template has gone all out of proportion while Ive been busy doing other things. Everything is too big. I haven't been working on it in months. But it was fine last times I saw it. Now it is all out of proportions. Can some one tell me how to fix? :idea:
thanks Ill PM link if interested
User avatar
Gold Boarder

GK User
Fri Sep 20, 2013 7:46 am
Could you show me your site URL ? It is always easier to check CSS/HTML code on live site.
User avatar
Platinum Boarder

GK User
Tue Sep 24, 2013 10:58 pm
IT IS HAPPENINNING COMPREHENSIVELY WITH INTERNET EXPLORER. IT IS OK ON FIREFOX.
PLEASE ADVISE ON WHAT TO DO :)
URGENT PLEASE HELP :mrgreen:
User avatar
Gold Boarder

GK User
Wed Sep 25, 2013 11:33 am
Please validate your site using W3C validator, probably there is some invalid code from module or content which cause this problem on IE.
User avatar
Platinum Boarder

GK User
Tue Oct 01, 2013 2:06 pm
Well I went to w3c and got this report which means little to me with my limited knowledge.
Where do I find this code to make the necessary alterations the validation errors suggest I make below?
I have not used anything other than what your template has supplied thats your supplied modules etc., SO I really am flying blind here and would like your help to fix this template so it shows properly in IE as I have not made any changes that I am aware of.


Validation Output: 6 Errors

Error Line 147, Column 55: document type does not allow element "div" here

…div id="facebox" style="display:none;"><div class="popup"><div class="content"…



The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Error Line 176, Column 243: there is no attribute "data-excluded"

… type='text/javascript' data-excluded='null' id='gkLazyLoad' src='http://shopp…



You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 442, Column 23: there is no attribute "ID"

<ul class="VMmenu" ID="VMmenu32528_55" >



You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Error Line 510, Column 35: an attribute value literal can occur in an attribute specification list only after a VI delimiter

<div class="boxSUFFIX" BORDER3""><div><h3 class="header">Shoppers Shopping<…



Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".
Error Line 545, Column 141: required attribute "alt" not specified

…down%20under%20tm%20construction.png" border="1" width="203" height="74" /></p>



The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Error Line 1001, Column 101: there is no attribute "autocomplete"

…form_password1" value="" autocomplete="off" class="validate-password required"…



You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

:blink: :silly: :huh:
User avatar
Gold Boarder

GK User
Thu Oct 03, 2013 9:29 am
Hmm... in the report there is no message that some closing tag is missed, the only errors comes from VirtueMart custom module but it is more warning than real problem. Please create some test product page where the description is empty, there are no images etc., and check how this look on IE. Please also disable all custom modules, plugins etc.,
User avatar
Platinum Boarder

GK User
Thu Oct 10, 2013 5:59 am
Hi I get this message in the back end
when I go to the 2 modules in question.



Module successfully saved
vmdebug self::$_jpConfig->lang en_gb
vmdebug vmTime: loadConfig db no: 0.00193095207214


also
not responding due to a long running running script

It is also deciding not to let me open individual modules sometimes. I have to try to or 3 times.


Also when I change and save how many rows and columns in the back end, thre front end reloads corectly and THEN goes to the wrong layout
Again IE only.
User avatar
Gold Boarder

GK User
Sat Oct 12, 2013 1:09 pm
Looks like problem with VirtueMart, please try to install this extension again.
User avatar
Platinum Boarder


cron