Errors and warnings from the W3C validator for plug-in generated code
-
Recently, I wanted to see in the W3C validator how my blog code looks like in terms of compliance of the html code with the W3C guidelines.
Unfortunately, WordPress and many plugins generate a lot of warnings and errors in this regard.
Also WebP Express generates more than 300 lines of errors and warnings on the indicated page. Can you please make corrections to the trivia?
On other pages, depending on the number of photos, the number of errors and warnings is proportional.The page I need help with: [log in to see the link]
-
Thanks for explanation. I also have the Jetpack plugin, which can also affect the code when publishing photos, especially since it sends them to the cloud server https://i1.wp.com/ (and similar addresses) and i found in file: jetpack-carousel.php: “array( ‘camera’, ‘aperture’, ‘shutter_speed’, ‘focal_length’, ‘copyright’ )”. I have also written to the authors of Jetpack, but have not received a reply yet.
Thank you very much for taking a look at the reported problem.
Anyway, it’s worth taking a look at your code generated in the page source to see if there are any redundant things or errors in it. Compliance with W3C is good practice, although many blogs in this area generate a lot of lines with errors, warnings, etc.Not waiting for Jetpack’s fixes, I replaced all PHP files ” />” and “/>” with “>”, and also commented out the meta so that the strings “{data-image-meta=”{” aperture”:”0″, “credit”:””,…” were no longer appearing. And looking at the validation of my entry:
https://validator.w3.org/nu/?showsource=yes&doc=https%3A%2F%2Fblog.tripsoverpoland.pl%2F2023%2F07%2F26%2Fmalbork-15-06-2023-zmiany-wokol-zamku-i-w-panoramie-zza-nogatu%2F
now the following errors are left for each photo:- Error: When the
srcsetattribute has any image candidate string with a width descriptor, thesizesattribute must also be specified.From line 42, column 1702; to line 46, column 1141ry__item"><img data-attachment-id="337191" data-permalink="https://blog.tripsoverpoland.pl/23_malbork_015/" da… data-image-title="Malbork 15.06.2023" data-image-description="<p>Malbork 15.06.2023</p>?" data-image-caption="<p>Malbork 15.06.2023</p>?" data-medium-file="https://blog.tripsoverpoland.pl/wp-content/uploads/2023/07/23_Malbork_015-650x61… data-image-title="Malbork 15.06.2023" data-image-description="<p>Malbork 15.06.2023</p>?" data-image-caption="<p>Malbork 15.06.2023</p>?" data-medium-file="https://blog.tripsoverpoland.pl/wp-content/uploads/2023/07/23_Malbork_015-650x61…land.pl/wp-content/uploads/2023/07/23_Malbork_015-1000x939.jpg?ssl=1" data-amp-layout="responsive"/></figu
Can you please take a look at the validator results for the code created by WEBP EXPRESS?Could you please take a look at the last reply from Jetpack:
https://github.com/Automattic/jetpack/issues/32819#issuecomment-1708425500 –“I see in your latest pdf that many of the specific errors you were complaining about in this task are no longer present with WebP Express disabled: the “no space between attributes”, “quote in attribute name”, complaints about bogus attribute names like “aperture”, etc. This is because WebP Express, being disabled, is no longer mangling attribute values that Jetpack has generated with correctly encoded
"characters.“True, there are still some errors relevant to Jetpack’s Carousel and/or Tiled Galleries features (e.g. “Duplicate attribute” and “srcset without sizes”) and other more generic errors (e.g. “trailing slash”), but those seem better covered under?#32818?or in yet-to-be-created subtasks that focus on those issues without the confusion in this task over all the errors caused by WebP Express’s mangling of Jetpack’s output.”
And please compare the results with the W3C for the WEBP EXPRESS plugin enabled:
https://tripsoverpoland.pl/ftp/WEBP_EXPRESS-ON-NuHtmlChecker.pdfand for plugin disabled:
https://tripsoverpoland.pl/ftp/WEBP_EXPRESS-OFF-NuHtmlChecker.pdf - Error: When the
- The topic ‘Errors and warnings from the W3C validator for plug-in generated code’ is closed to new replies.
