W3C Validation

Home Forums Calendar Products Events Calendar PRO W3C Validation

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #847126
    sadrobot
    Participant

    Hello. I’m currently developing quite a large site and I’m in the middle of cleaning it up to make sure it validates at W3C. Unfortunately, the only error I am receiving relates to Events Calendar, and the usage of ‘&’ in the URLs. I feel like I’ve gone through the entire source code and updated them all to ‘&’, but it still doesn’t work. I’m lost as to where the script is that generates the URLs from the widgets. The W3C check can be found here:

    http://validator.w3.org/check?uri=http%3A%2F%2Fhexagon.org.uk.91-102-64-135.preview.fastwebhosting.net%2Fleaseholders-handbook%2Fwhat-to-expect&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices#line-547

    Please could someone direct me to the right script so I can find and update it? Hope someone can help!

    Thanks!

    #847128
    sadrobot
    Participant

    Sorry, my above example replaced my usage of ‘& amp;’ to ‘&’. 🙂

    #848782
    Brook
    Participant

    Howdy sadrobot,

    Thanks for pointing this out. That does look to be a bit of a bu in the code on our end. Usually URLs are run through URL espcaing before being echoed, but in this case it looks like one is not. I will reports this to the devs so they can fix it.

    In the interim, I bet if you switched to “pretty URLs” this error would disappear. Furthermore, many people state that a site looks more professional and gets better search engine performance. This can be accomplished by going to WP Admin > Settings > Permalinks and changing the option to anything but the default.

    Does that answer your questions? Is there anything else I can help with? Please let me know!

    – Brook

    #849341
    sadrobot
    Participant

    Hi Brook. Thanks for the fast response! That does make sense and switching to pretty URLs would probably solve the problem. It’s just unfortunate that another plugin I’m using doesn’t work with Pretty URLS – hence it being turned off. But I’ll wait for that other plugin to be updated! Thanks again.

    #849874
    Brook
    Participant

    Well that’s not a good option. I think I figured out a way to solve this in the interim. Try pasting this snippet in your theme’s functions.php file: http://pastebin.com/swhxx0FX That solved things on my end. Please let me know if it works! I have not had a chance to test it super thoroughly, but I see no reason it would have side-effects. Cheers!

    – Brook

    #850077
    sadrobot
    Participant

    Thanks a lot for looking into this for me! I have pasted it into my functions file and while it worked – it only worked once. I had two errors previously, but after pasting the code in, I only have one! 🙂
    http://validator.w3.org/check?uri=http%3A%2F%2Fhexagon.org.uk.91-102-64-135.preview.fastwebhosting.net%2Fabout%2Fservices&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%2Fvalidator.w3.org%2Fservices

    Do I also need to apply it to another ‘occurence’? :/

    Thanks again, though, it’s smashing what you’ve done 🙂

    #859136
    Brook
    Participant

    Howdy sadrobot,

    I do not believe you have errors anymore. When I click that link it shows up proper. It does mention a warning, but those tend to not be requirements and more suggestions. If you wanted to address it feel free, you would want to add a heading tag somewhere in the content area of your posts including events. Make sense? Is it resolved now for you as well? I am happy to help!

    – Brook

    #906866
    Brook
    Participant

    Since this topic has gone for a couple of weeks without a response I going to archive it. If for some reason this issue is not resolved though, please open a new topic. We are happy to continue helping!

    – Brook

Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘W3C Validation’ is closed to new replies.