First, thanks for the new layout of the plugin check page.
Have version 1.0.1 installed. For all plugins a wrong warning is returned:
FILE: readme.txt
The plugin readme.txt does not exist.
Guido
]]>Google indexed the main sitemap url (../sitemap.xml), but following the link it didnt discovered the rest: …/sitemap-posttypes, it shows: could not get (no further info from google side)
I’ve submitted those urls, included the sitemap.xml on a sitemap validator (xml-sitemaps.com) and it says:
Incorrect http header content-type: “text/html; charset=UTF-8” (expected: “application/xml”)
the site runs under cloudflare, I’ve created a cache rule so those sitemaps wont be cached, but the error persists.
Any suggestions? Thank you!
]]>“Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.”
Can you please remove the slash “/>” and make it like this “>” for these html elements:
<meta, <link, <input, <img.
I know it’s not an error, but the more of these “Info” comments I can remove, the better it is. Thanks.
]]>I have problem with my feed. Two Errors are appearing on feed validator. Could you help me fix that?
]]>We use mailpoet to send post notifications to email subscribers when posts are published.
Today we discovered it had sent 5 notifications of a new post even though nothing new had been published.
Using Activity Log I discovered that something to do with amp_validation is editing the publishing dates of the “amp_validated_url” post types.
I’m thinking this is the cause of the multiple notification issue. Why is the AMP validator changing the published dates on posts?
Thanks,
Mik
Some fixes for AMP issues failed for site https://www.sinapsi.org/
You sent Google a request to validate the AMP problem fix at https://www.sinapsi.org/. The requested fix involved the following problem: “JavaScript code is not allowed.”.
However, we have found that the problem is still present on some pages.
During the validation we were able to verify that the problem is no longer present in 45 pages of the site.
Follow this link for full details of the validation process and for information on how to resolve the issue on the remaining pages.
]]> Error: CSS: Parse Error.
At line 549, column 30
padding .box>.details:after
Error: CSS: Parse Error.
At line 549, column 75
-padding.box>.details:after
Error: CSS: Parse Error.
At line 552, column 44
search-box > ul.search-tabs
Error: CSS: Parse Error.
At line 552, column 74
li.active > a { border: 2p
Error: CSS: Parse Error.
At line 562, column 29
xt-wrapper > div {line-heig
]]>