Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted April 10, 20213 yr My site gets tons of w3 HTML validation errors for the social mailto sharing link. I noticed that this forum does not use the same type of social sharing links as the default ones in the current version of IPS. Does anyone know how to fix these errors?
April 10, 20213 yr Author After more experiments, it seems I had to change the "?subject={$title}" from the email sharing template to something like: ?subject=Article_from_Mysite.com Not an ideal solution, but it avoids the many validation errors I am seeing. A better solution would be to have the ability to have the same pop up that is used on this site for the social links. When will that be available in a current release? Edited April 10, 20213 yr by sadams101
April 12, 20213 yr Author I have another w3 validation issue to report. If you use the calendar block on your site, for example on desktop see the bottom right-right of my site: https://www.celiac.com/articles.html/should-doctors-recommend-a-gluten-free-diet-for-all-elderly-celiac-patients-r5498/ the calendar time format throws errors like this, and it doesn't seem to matter whether you set a specific time for the event or not (I had my events as "all day" and then changed them to having a start and end time, but the errors are the same: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.celiac.com%2Farticles.html%2Fshould-doctors-recommend-a-gluten-free-diet-for-all-elderly-celiac-patients-r5498%2F Error: Bad value 2021-04-23 0:0:0 for attribute datetime on element time: The literal did not satisfy the time-datetime format. From line 4294, column 7; to line 4294, column 64 ↩ <time datetime='2021-04-23 0:0:0' class='ipsCalendarDate'>↩ : Edited April 12, 20213 yr by sadams101
April 12, 20213 yr Author PS - Why wait until version 4.6 to fix html errors? This is an easy patch...
April 12, 20213 yr 1 hour ago, sadams101 said: I have another w3 validation issue to report. If you use the calendar block on your site, for example on desktop see the bottom right-right of my site: https://www.celiac.com/articles.html/should-doctors-recommend-a-gluten-free-diet-for-all-elderly-celiac-patients-r5498/ the calendar time format throws errors like this, and it doesn't seem to matter whether you set a specific time for the event or not (I had my events as "all day" and then changed them to having a start and end time, but the errors are the same: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.celiac.com%2Farticles.html%2Fshould-doctors-recommend-a-gluten-free-diet-for-all-elderly-celiac-patients-r5498%2F Error: Bad value 2021-04-23 0:0:0 for attribute datetime on element time: The literal did not satisfy the time-datetime format. From line 4294, column 7; to line 4294, column 64 ↩ <time datetime='2021-04-23 0:0:0' class='ipsCalendarDate'>↩ : I believe that has already been fixed as part of a different unrelated issue. 43 minutes ago, sadams101 said: PS - Why wait until version 4.6 to fix html errors? This is an easy patch... We issue patches for critical or wide-impacting issues. These validation errors would not qualify as one of those.
April 12, 20213 yr Author Regarding the calendar HTML errors, I am running the latest version, and the block is still throwing those errors.
April 13, 20213 yr 16 hours ago, sadams101 said: Regarding the calendar HTML errors, I am running the latest version, and the block is still throwing those errors. Sorry, the mentioned fix is in 4.6, not a currently released version.
April 13, 20213 yr Author Any chance you can share the fix for the calendar issue here? Google is now penalizing pages that have too many W3 errors, so I am fixing those errors. The use of the "scrolling" attribute when you share links to articles within posts is causing W3 errors. Example: https://www.celiac.com/forums/topic/154906-advice-please-waiting-to-be-diagnosed/?tab=comments#comment-1086093 https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.celiac.com%2Fforums%2Ftopic%2F154906-advice-please-waiting-to-be-diagnosed%2F%3Ftab%3Dcomments%23comment-1086093 Is this also fixed in 4.6, and if so, can you share the fix here?