Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Simpatico

    (@simpatico)

    Some of the site having these file count problems with w3tc.

    health-fitness.mobi
    healthy-recipe.info
    xgf.me

    Thread Starter Simpatico

    (@simpatico)

    question to w3tc.
    How many files does a typical install of w3tc create ?

    Thread Starter Simpatico

    (@simpatico)

    W3TC contacted me very promptly, their support is excellent.
    I was asked to fill out a bug report, but can not locate, so I will try to give more information here.
    Maybe related: It appears w3tc was updated recently, I get messages in wordpress admin that I can delete w3tc directory but not w3tc.config. deleting the w3tc director using a Fpt connection to Godaddy took over 24 hours 3500 files.
    The problem with file count at Bluehost according to Bluehost is the WP-content/cache directory which creates thousands of directories with no files in them.

    Thread Starter Simpatico

    (@simpatico)

    The new site is

    http://hot-funny-you-tube-videos-calientes-homemade-music-dvds-online.com

    I guess more than one link will not post in the same thread.

    Thread Starter Simpatico

    (@simpatico)

    The new link to the new site did not post in the above

    Thread Starter Simpatico

    (@simpatico)

    These errors are in WordPress right out of the box as installed by GoDaddy. All three errors are related to “roll”. Can anyone help me correct them ?

    Validation Output: 3 Errors

    1. Error Line 30, Column 23: there is no attribute “role”

    <div id=”header” role=”banner”>

    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.
    2. Error Line 65, Column 16: there is no attribute “role”

    <form role=”search” method=”get” id=”searchform” action=”http://hot-funny-y…

    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.
    3. Error Line 79, Column 12: there is no attribute “role”

    <ul role=”navigation”>

    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.

    Forum: Themes and Templates
    In reply to: code bebugging
    Thread Starter Simpatico

    (@simpatico)

    OK

    Thank you

Viewing 7 replies - 1 through 7 (of 7 total)