Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter Rodrigo

    (@rghedin)

    Up?

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    Hi @rghedin!

    Thank you for bringing that to our attention.

    Currently, we allow only a few tags in the feed – <p>,<a>,<ul>,<ol>,<li>,<strong>,<em>.

    But I don’t see any harm if we add header tags to this list as well. This change will be available in the next plugin release.

    Best regards,
    Sergiy, development team.

    Thread Starter Rodrigo

    (@rghedin)

    Awesome, @zahardoc! I’m looking forward this next release. Thanks! ??

    Thread Starter Rodrigo

    (@rghedin)

    @zahardoc, glad to see that this changing made its way to a release. Tested here and it’s working fine!

    I noticed, however, a differente-but-related issue with <p> tags: they get vanished from SSP’s RSS unless I declared them using HTML editor. (I’m still using WordPress’ Classic Editor, btw.) If I just hit Enter (rich text editor) or double-Enter (HTML), which in WordPress automatically add <p> tags, they are ignored in SSP’s feed.

    It’s a minor issue because there’s a workaround (write posts in HTML editor and write <p> tags), but I guess you’d like to know and, maybe, fix this in a upcoming update.

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    Hi @rghedin!

    Glad it works for you now!

    Regarding the <p> tag – we didn’t change anything on the plugin side from that perspective. I think something might have been changed in WordPress itself.

    Thread Starter Rodrigo

    (@rghedin)

    This issue with <p> tag predates this latest update. I was about to warn you guys but forgot to ??

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    @rghedin

    Please try putting this code snippet in your functions.php file:

    add_filter( 'ssp_feed_item_content', function ( $content ) {
    	return wpautop( $content );
    } );
    Thread Starter Rodrigo

    (@rghedin)

    It didn’t work, @zahardoc, as you can see in this post/podcast.

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    @rghedin

    Sorry I couldn’t help you with the p issue, though it did work on my site.

    The problem is that if you use Classic Editor WP itself doesn’t save the content with p tags. So maybe the best solution here would be just using HTML editor.

    Thread Starter Rodrigo

    (@rghedin)

    It’s a shame since the lack of <p> tag doesn’t affect WordPress’ front-end. Thanks for your reply, @zahardoc!

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    @rghedin

    Yes, because WordPress adds <p> tags automatically before putting text to front-end.

    I mean it converts newlines into paragraphs. And that is what I was trying to do when advised the filter in my previous posts ( with wpautop() function ). I’m not sure why it didn’t work on your site though.

    Thread Starter Rodrigo

    (@rghedin)

    A added that snippet again, just in case. (I guess it can’t hurt even if it doesn’t work, right?)

    Thanks, @zahardoc!

    Plugin Author Serhiy Zakharchenko

    (@zahardoc)

    @rghedin

    Yes, I believe it won’t hurt.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘SSP can’t parse H2 tags?’ is closed to new replies.