Instant Update 3.2 and W3C Compliancy?
  • Hi,

    A couple of areas to cover in this really,

    currently I have developed a single page XHTML, CSS Driven page and incorporated Instant Update 3.2 in the background, now I am looking at the W3C side of this and only a few small areas that are causing me problems, errors & warning shown below? now as the content is dynamic and PHP / JavaScript is a weak point of mine slightly, I am unable to determine exactly what I need to amend to remove the offending code.

    The two errors:

    ///////// ERROR 1 ///////////
    Line 111, Column 67: required attribute "ROWS" not specified
    …xtarea name='message' id='cform-message' class='cform-textarea'>

    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 and type="text/javascript" for .


    ///////// ERROR 2 ///////////
    Line 111, Column 67: required attribute "COLS" not specified

    …xtarea name='message' id='cform-message' class='cform-textarea'>

    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 and type="text/javascript" for .


    I simply need to have the script within the contactform.plugin.php page amended to allow for the contact form(s) to contain the required rows and columns attribute. Could someone advise what part of the script exactly needs to be adjusted and with what?




    The next warnings are also related to the contact form at this stage as shown below:
    (there are more but once I see how one or two need to be adjusted I can repeat across all accordingly)

    ///////// WARNING 1 ///////////
    Line 42, Column 118: NET-enabling start-tag requires SHORTTAG YES
    …l Electrical Engineer & Contractor Services" />


    The sequence can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag '). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

    ///////// WARNING 2 ///////////
    Line 107, Column 56: NET-enabling start-tag requires SHORTTAG YES


    The sequence can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag '). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.


    Again as these are being dynamicly created I can not just removing the offending / from the input fields script, Could someone advise what part of the script exactly needs to be adjusted and with what?


    Lastly the menu's populated by Instant Update are also causing issues (although not used in this particular draft template) these have shown to fail the W3C compliance test in the past as well, only due to the repeated same ID tag of menueitem if I remember correctly. Could someone advise what part of the script exactly needs to be adjusted and with what?


    And finally but a little off topic, I have purchased the unlimited licence, once I have completed the above tasks and successfully managed to utilise all of the IU 3.2 features and functions and made sure these all comply to W3C standards, I plan to develop and sell IU 3.2 templates based on the IU 3.2 platform for very small sole traders, tradesmen etc. and even to small business in need of a valuable on-line presence, as far as I can see this would not be breaching your terms and conditions of use but would like written clarification from your team just to make sure this is ok with your team for me to start offering / selling templates designed for use with IU 3.2 ready for IU 3.2 users to upload with there IU 3.2 package purchased from Cube Scripts and / or packaged as a final end product for people who approach us direct that we install on our hosting companies servers the IU 3.2 software purchased buy us in the past, and deploy with one of our templates at a cost to the client?

    Could you please confirm that this is not in breach of your terms or conditions and that your are happy for us to provide such products and / or services to both public and business sectors alike.

    Thank you in advance for any assistance with any / all of the above

    We look forward to your response shortly.

    Regards

    S.Willett
    Duello Media (Formerly SMW Group)
  • Take a look at following file:
    manage/plugins/iu-contact-form/contactform.plugin.php

    Around line #65 find this:

    <textarea name='message' id='cform-message' class='cform-textarea'></textarea>


    Replace it with this:

    <textarea name='message' id='cform-message' class='cform-textarea' rows='8' cols='20'>
    </textarea>


    Play with those values (8/20) to suit your site visual needs.

    I couldn't figure out what those other two warnings are referring to?
  • For menu, open up manage/functions.php, around line 196 find this

    $the_id = ' id="menuitem"';


    and replace it with this:


    $the_id = '';


    This id is not used anymore so I think it can be safely removed.

    About your other question (about licenses), I'll let Tomo answer that.
  • Avram,

    Thank you, I managed to finally get the time to re-visit this today and this has worked wonders, I look forward to hearing from Tomo over the coming days or week hopefully in regards to the licensing query. (Overall result, passed but still with the 29 warnings)

    The current script being produced is:

    <form action='./manage/plugins/iu-contact-form/process.php' id='cform-form' method='post' onsubmit='return cform_sendEmail();'>
    <input type='text' name='subject' class='cform-hidden' />
    <p>Name: <br /> <input type='text' name='name' id='cform-name' value='' class='cform-input' /></p>
    <p>Email: <br /> <input type='text' name='email' id='cform-email' value='' class='cform-input' /></p>
    <p>Message: <br />
    <textarea name='message' id='cform-message' class='cform-textarea' rows='8' cols='20'></textarea></p>
    <br />
    <p><input name='image' type='image' class='cssimage' title='send' value='SEND' src='./manage/plugins/iu-contact-form/imgs/send.png' alt='send' /></p>
    </form>


    As you can see this is populating the input fields etc with the shorthand / (Forward slash) This is what the warning appear to be referring too but not totally sure how this is being created as I cna not find the file containing the form regions etc.



  • Hello,

    Can you please open sales support ticket so we can continue with licensing communication. There are of course some limitations how to use and resell our software.

    http://my.cubescripts.com/support/index.php?/Tickets/Submit


    Thanks.

  • Everything related to contact form (like html form) is located in already mentioned file: manage/plugins/iu-contact-form/contactform.plugin.php

    Lines 58-68 define look of contact html form. You can remove /> and put only > there to make form HTML valid.
  • Avram,

    A total oversight on my part, thank you again for this.

    Last couple of tweaks and test then should be 100% W3C compliant! woo hoo!

    I know a lot of people overlook this area but I feel it contributes towards a cleaner WWW.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!