• Resolved crusy

    (@crusy)


    The following minimal setup will trigger the problem:

    [include-mastodon-feed instance="chaos.social" account="111784504453496359"]

    This will lead to a closing </p> tag in the DOM, at least until the feed is fetched.

    Seems to me that during the initialization of the feed a div with id include-mastodon-feed-<someHash> is replacing a placeholder paragraph in the blog’s widget area, but only the opening <p>, leavin the closing </p> in place..? You can verify when using https://validator.w3.org/ which does not load the JS-based feed, hence complaining about said </p>.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Wolfgang

    (@wolfgang101)

    Hi. I looked at your blog and if I’m not mistaken you are using this theme that is from 2016? https://www.ads-software.com/themes/ari/

    The additional <p> tags are not produced by the plugin, but rather your WordPress installation. Best recommendation I can give is to use a contemporary theme that supports modern features like the WordPress Gutenberg block editor.

    When using either the “custom HTML” or “shortcode” block you will not get the <p> tags. Not sure what the corresponding widgets pre Guttenberg were. IIRC there was a “custom HTML” widget element too. Maybe also a shortcode element? Using those instead of a WISYWIG element will get rid of the <p> tags.

    Thread Starter crusy

    (@crusy)

    Thanks a lot, I will try that.

    PS: Sorry for double posting here and on Github. This topic here was marked as spam first, and then supposedly deleted. I wrote the Github issue after that “deletion”. Thanks again.

    Plugin Author Wolfgang

    (@wolfgang101)

    Update after more debugging (and for other users that face a similar issue).

    We tested the Custom HTML and Shortcode block inside a sidebar widget. The Custom HTML block produced clean output, but the shortcode block added <p> tags.

    After further research this seems to be a known issue since 17 years https://core.trac.www.ads-software.com/ticket/6984

    There are even plugins that try to mitigate the issue, but an easy workaround that seems to work fine right now is to just wrap the shortcode inside a <div>.

    This worked inside a shortcode block inside a sidebar widget:

    <div>[include-mastodon-feed instance="chaos.social" account="111784504453496359"]</div>
Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.