Resolving Quote Issues

While the Quote might sound as a straightforward feature to have, there are potential issues and challenges in Quotes implementation that may need to be resolved.

Why when quoted, emojis (or smileys) are displayed broken?

This happens because WordPress, by default, is replacing all emojis with images. This is done so that emojis would work in old browsers. But, the JavaScript used for this purpose can slow down the website, messing with the page loading only to show very old and outdated images instead of the pretty emojis most browsers have today.

Disabling WordPress emoji replacement is the only way to avoid the problem with quotes and emojis. With GD bbPress Toolbox Pro, you can use the Features -> Tweaks -> Processing Content for Display -> Disable Smilies Conversion and set it to Enabled.

Why quoted content shows HTML tags?

In bbPress, only some user roles can post unrestricted HTML content. Other users can only use some basic set of HTML tags, and tags like UL, LI, and DIV… will not work, and bbPress will save them as text, not HTML. Because of that, when you quote complex HTML content, tags normally not supported will be displayed as text, not HTML.

To fix this, you must allow all user roles to use the expanded set of HTML tags. And to do that, open the bbPress Toolbox -> Features -> Tweaks -> Expand KSES allowed HTML tags and attributes -> Allowed tags list .The Select box has 3 options: the default bbPress set of HTML tags, and the other two include a wide range of supported HTML tags. You need to switch this option to the second or third option.

But, some HTML tags are not permitted (IFRAME, SCRIPT, STYLE) because they can generally contain dangerous content, and when quoted, such tags will be escaped and saved as plain text. Because of that, quoting content that contains embedded content (FaceBook posts, Twitter tweets…) is not quotable.

Rate this article

You are not allowed to rate this post.

Leave a Comment