Hi Alex,
Thank you for your message. First of all these are warnings and not errors. It has no impact on the actual plugin’s normal behaviour so no worries.
That being said, the DOMDocument class is know to trigger warnings when stumbling upon HTML5 tags such as <figcaption>. It does still process them well though.
To prevent these warnings from showing, we can add a libxml_use_internal_errors(true); clause before.
I will make sure to have this added in the next update 😉
Thanks for your quick answer, ok.
If it’s ok to post here, without creating a new support message: I saw another error message after updating to the new version:
But I don’t have the toc in a widget, just in the content area of a normal page. Anyway I can activate widget support (which I don’t need) and the message disappears. Just wanted to tell you.
And one more thing: screaming frog gives a high warning that there are 2 <body> .. marks on each page because of joli toc.
I’m not sure if this is an important impact on the site.