During the validator check i am stuck on just 1 error..
Error Line 8, Column 30: Bad value title for attribute name on element meta: Keyword title is not registered.
name="title" content="Home" /><meta
Had this same error on TW2 and after modifying /layouts/default.php i managed to fix this....However for this template i am stuck...Could you please help me out? my website is veptalentjes.nl
This is the first part of thesource and the last line would be the "error"
<!DOCTYPE html><html
prefix="og: http://ogp.me/ns#" lang="nl-nl" ><head>
<meta property="fb:app_id" content="" /><meta
name="viewport" content="width=device-width, initial-scale=1, maximum-scale=2.0"><base
href="http://veptalentjes.nl/" /><meta
http-equiv="content-type" content="text/html; charset=utf-8" /><meta
name="keywords" content="Vep,F7, F10, F3, Woerden, HomeVoetbal leukste" /><meta
name="title" content="Home" /><meta
One error when checking the template at W3c validator
Rate this topic: 
1.00 out of 6 based on 1 vote(s)
1.00 out of 6 based on 1 vote(s)- GK User
- Fri Feb 07, 2014 8:17 pm
- Reply with quote
- Report this post
Not sure if i understand...Where do change this to be W3C compliant?
-
- Senior Boarder
- GK User
- Sat Feb 08, 2014 8:15 am
- Reply with quote
- Report this post
You are asking where - but how would you like to modify this code? How should it look after modification?
-
- Moderator
- GK User
- Sun Feb 09, 2014 11:14 am
- Reply with quote
- Report this post
I just want get this error fixed...http://validator.w3.org/check?uri=http% ... ne&group=0
Could you point me the right direction...
Could you point me the right direction...
-
- Senior Boarder
- GK User
- Tue Feb 11, 2014 8:13 pm
- Reply with quote
- Report this post
From what I see, there is no such tag in current J3.x News template.
1. Try updating the template first
2. If above will not help, please switch to one of the default templates and check if this line is still there.
1. Try updating the template first
2. If above will not help, please switch to one of the default templates and check if this line is still there.
-
- Moderator
- GK User
- Tue Feb 11, 2014 9:54 pm
- Reply with quote
- Report this post
No luck in updating gk_news....Even switching to twn2, has the same result...So presume this caused by JOOMLA itself?
-
- Senior Boarder
- GK User
- Wed Feb 12, 2014 8:50 am
- Reply with quote
- Report this post
Last test - please check if on default beeze template it behaves same. Perhaps you use some 3rd party plugin that puts this into header?
-
- Moderator
- GK User
- Wed Feb 12, 2014 9:07 am
- Reply with quote
- Report this post
When using beeze3 i get the below result.... The error goes from line 8 to line 17........
Validation Output: 4 Errors
Error Line 12, Column 41: Bad value HandheldFriendly for attribute name on element meta: Keyword handheldfriendly is not registered.
name="HandheldFriendly" content="true" /><meta
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Error Line 17, Column 30: Bad value title for attribute name on element meta: Keyword title is not registered.
name="title" content="Home" /><meta
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Error Line 245, Column 26: End tag div seen, but there were open elements.
id="system-message"></div><span
✉
Error Line 245, Column 20: Unclosed element dl.
id="system-message"></div><span
Validation Output: 4 Errors
Error Line 12, Column 41: Bad value HandheldFriendly for attribute name on element meta: Keyword handheldfriendly is not registered.
name="HandheldFriendly" content="true" /><meta
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Error Line 17, Column 30: Bad value title for attribute name on element meta: Keyword title is not registered.
name="title" content="Home" /><meta
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Error Line 245, Column 26: End tag div seen, but there were open elements.
id="system-message"></div><span
✉
Error Line 245, Column 20: Unclosed element dl.
id="system-message"></div><span
-
- Senior Boarder
- GK User
- Wed Feb 12, 2014 11:39 am
- Reply with quote
- Report this post
As you can see there is the same problem:
So its not our template problem, but more joomla kind.
- Code: Select all
<name="title" content="Home" />
So its not our template problem, but more joomla kind.
-
- Moderator
- GK User
- Thu Feb 13, 2014 9:50 am
- Reply with quote
- Report this post
Would this article apply, and if so where do i apply this? in default.php?
http://catdevblog.nickbair.net/2013/06/ ... oomla-3-0/
http://catdevblog.nickbair.net/2013/06/ ... oomla-3-0/
-
- Senior Boarder
- GK User
- Thu Feb 13, 2014 11:15 am
- Reply with quote
- Report this post
You can try placing it in index.php just befode closing:
- Code: Select all
?>
-
- Moderator
- GK User
- Fri Feb 14, 2014 10:30 pm
- Reply with quote
- Report this post
So far only found out that it comes with the K2 item set as homepage....When setting a category or joomla item it does not give the error...
Any idea ?
Any idea ?
-
- Senior Boarder
- GK User
- Mon Feb 17, 2014 8:05 am
- Reply with quote
- Report this post
As I have said - it has nothing to do with our template. If you think its because of k2, please ask on their forum, as we only uses k2 as a plugin/module.
-
- Moderator
- GK User
- Tue Feb 25, 2014 11:07 pm
- Reply with quote
- Report this post
Ok have changed mt startpage from a K2 item to joomla article and the error is gone...However it comes up with these 2 now. When disabling the options in the template they are gone.....
Warning Line 626, Column 150: Element name fb:like cannot be represented as XML 1.0.
…es="true" width="500" action="like" font="arial" colorscheme="light"></fb:like>
✉
Error Line 626, Column 150: Element fb:like not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
…es="true" width="500" action="like" font="arial" colorscheme="light"></fb:like>
Content model for element div:
Flow content.
Error Line 629, Column 121: Attribute gk_tweet_btn_settings not allowed on element a at this point.
…ter-share-button" data-text="Home" data-url="" gk_tweet_btn_settings>Tweet</a>
Attributes for element a:
Global attributes
href
target
download
rel
hreflang
type
Warning Line 626, Column 150: Element name fb:like cannot be represented as XML 1.0.
…es="true" width="500" action="like" font="arial" colorscheme="light"></fb:like>
✉
Error Line 626, Column 150: Element fb:like not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
…es="true" width="500" action="like" font="arial" colorscheme="light"></fb:like>
Content model for element div:
Flow content.
Error Line 629, Column 121: Attribute gk_tweet_btn_settings not allowed on element a at this point.
…ter-share-button" data-text="Home" data-url="" gk_tweet_btn_settings>Tweet</a>
Attributes for element a:
Global attributes
href
target
download
rel
hreflang
type
-
- Senior Boarder
- GK User
- Sat Mar 01, 2014 8:15 am
- Reply with quote
- Report this post
The first error is because w3c validator doesn't know xfbml language used by facebook snippet.
With the second one - I'll ask our dev team why twitter button renders this way.
Ps. You need to know, that w3c is just a roadmap and you should treat it as a suggestions not "must to do". Understanding what each error means and if it is crucial for fixing (like not closed html tags etc) or just an info is up to user, and only with that knowledge w3c validator should be approached.
With the second one - I'll ask our dev team why twitter button renders this way.
Ps. You need to know, that w3c is just a roadmap and you should treat it as a suggestions not "must to do". Understanding what each error means and if it is crucial for fixing (like not closed html tags etc) or just an info is up to user, and only with that knowledge w3c validator should be approached.
-
- Moderator
16 posts
• Page 1 of 1