SEOTools2 broken W3C Validity [Solved]

[CRSounds]

I have installed SEOTools2 to try and improve my seo and it appears to have broken my W3C Validity.
The site was working before and appears to be working ok now except it throws loads of errors in the W3C Validator tool http://validator.w3.org/check?uri=http% ... 2Fservices

It appears to be missing a load of end tags which it quite worrying. Although the site seems to be working fine http://crsounds.co.uk

I followed the module help setup instructions to the letter.
Anyone any ideas what could be the cause?

[paulbaker]

A lot of the errors are missing end tag, e.g.

Code: Select all

<meta name='geo.placename' content='Bedfordshire'>

The end bit should be

Code: Select all

content='Bedfordshire' />

Browsers are very forgiving of that particular error though.

[CRSounds]

Hi Paul, yes I see there are a lot of these errors.
These have only appeared since SEOTools2 was installed and set up though.
So I guess my question is have I configured SEOTools2 wrong or is there a problem with the plugin?

[staartmees]

Notice: This project is marked as stale. This means that it may work fine, but it has no file releases or repository commits in over a year. Use your own discretion when using this project.

None of the bugs have been solved since 2012.

[paulbaker]

SEOTools2 works fine for me

Don't forget the W3C Validator tool compares your HTML to the exact specifications. Just because it breaks some trivial rules doesn't mean it won't work perfectly well in every modern browser....and that's the important thing.

[psy]

SEOTools2 is sensitive to the HTML version you are using. Make sure you have it set correctly in the dropdown on the Page Title & Metadescription tab.

The default is HTML5. The errors you are seeing will occur if your template is set for XHTML.

[CRSounds]

Ah ha. Cracked it. Seo tools was set to html5. Set it to xhtml to match my template and most of the errors have gone. Thanks psy and everyone for the input . Great support.

[psy]

None of the bugs have been solved since 2012.

Most of the bugs were Invalid due to user error/lack of knowledge.

There are a couple that are trivial and do not affect the performance of SEOTools2 or CMSMS.

I have also received a few feature requests but time and resources dictated that 'if it ain't broke, don't fix it'.

Happy to release a new version simply to remove the stale notice in the forge...

psy

[psy]

Having said that, there are a couple of things I'd like to tweak so maybe a new version sometime soon. Wont be anything dramatic though.

The current 'stale' version still works well with the latest version of CMSMS.

[psy]

CRSounds, please add [solved] to the topic subject

[Rolf]

Having said that, there are a couple of things I'd like to tweak so maybe a new version sometime soon. Wont be anything dramatic though.

The current 'stale' version still works well with the latest version of CMSMS.

In the Forge the module admin can remove the stale message. there is a button for this.