-
Posts
-
Hi Team,
Nu Html Checker found some errors in my Enfold Website…
It seems that the “Stray end tag div” comes in all Mansory views, the other at all pages.http://http://www.exusu-design.de:
- No p element in scope but a p end tag seen. From line 257, column 1; to line 257, column 4
- A charset attribute on a meta element found after the first 512 bytes. At line 17, column 21
- Bad value https://api.w.org/ for attribute rel on element link: The string https://api.w.org/ is not a registered keyword.
- Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.) From line 324, column 1; to line 324, column 46
http://www.exusu-design.de/profil-exusudesign/ :
- A charset attribute on a meta element found after the first 512 bytes. At line 17, column 21
- Attribute color not allowed on element link at this point. From line 109, column 1; to line 109, column 108
- Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)
http://www.exusu-design.de/guter-start-gruendercoaching/ :
- No p element in scope but a p end tag seen. From line 230, column 1; to line 230, column 4
http://www.exusu-design.de/portfolio/ :
- Stray end tag div. From line 265, column 24; to line 265, column 29
http://www.exusu-design.de/wordpress/ :
- No p element in scope but a p end tag seen. From line 254, column 1; to line 254, column 4
- A charset attribute on a meta element found after the first 512 bytes. At line 17, column 21
- Attribute color not allowed on element link at this point. From line 109, column 1; to line 109, column 108
- Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.) From line 333, column 1; to line 333, column 46
http://www.exusu-design.de/blog/ :
- Stray end tag div. From line 265, column 24; to line 265, column 29
Kontakt
- No p element in scope but a p end tag seen. From line 209, column 29; to line 209, column 32
Hope you will find an solution! Thanky you.
Regards
MikeHi,
Are you suffering from any problems due to this or is it a strictly academic problem?
Thanks,
RikardHi Rikard,
I don’t really underdstand you question. Incorrect closing <p> and <div> are not academic!
(That’s why I made this lines bold ;). I think I don’t have to say you what kind off trouble an
site can get with this?!Regards
MikeHey!
Thank you for bringing this to our notice.
Enfold’s Advanced Layout Builder is tightly integrated in the theme to create advanced layouts with the right html code.
The reason you are seeing these errors could be dude to customization of the theme or any plugin conflict.Please deactivate all the plugins and child theme customization before running the check again and let us know your results so i can update our devs about it with the same.
Regards,
VinayHey!
I think any advanced WordPress theme will have some errors with such kind of html validators. Only basic WordPress theme won’t have any. If you want to make sure that your theme files aren’t corrupt then please delete all theme files completely via FTP, before installing a fresh copy from your themeforest account: http://kriesi.at/documentation/enfold/install-enfold-over-ftp/
If you see any real problems on your website (frontend), then please provide us some screenshots to highlight the issue for us.
Best regards,
AndyHi Andy,
shure, I totally agree with your point. But unclosed p oder div are not an typically error for an advanced theme,
this is more an typically failure – sorry. And when there are no problems with the frontend, then is this luck and
it will be better to fix this in on off your updates ;)Regards
MikeHey!
there are lots of improvements and fixes which need Kriesi’s attention. I think it would be best to focus on the most important things first.
Regards,
AndyThe banner role is unnecessary for element header.
<header↩id=’header’ class=’all_colors header_color light_bg_color av_header_top av_logo_left av_main_nav_he…eader_border_disabled’ role=”banner” itemscope=”itemscope” itemtype=”https://schema.org/WPHeader” >
– – – –
Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)data-av_icon=’’ data-av_icon
– – – –Element nav does not need a role attribute.
From line 52, column 57; to line 53, column 111
<nav↩class=’sub_menu’ role=”navigation” itemscope=”itemscope” itemtype=”https://schema.org/SiteNavigationElement” ><ul↩idHi,
thanks, I’m sure Kriesi will fix it at some point, but as already said: most important bugs/improvements first.
Best regards,
Andy
- You must be logged in to reply to this topic.