PluginProbe
ActivityPub / 9.2.1
ActivityPub v9.2.1
9.3.1 9.3.0 9.2.2 9.2.1 9.2.0 9.1.0 9.0.2 9.0.1 9.0.0 8.3.0 8.2.1 8.2.0 8.1.1 1.0.5 1.0.6 1.0.7 1.0.8 1.0.9 1.1.0 1.2.0 1.3.0 2.0.0 2.0.1 2.1.0 2.1.1 All 160 releases
← All changes | includes/functions-comment.php +0 -27 9.3.0 → 9.2.1 View file →
@@ -215,31 +215,4 @@
215 215 $url = \apply_filters( 'activitypub_reply_intent_url', $url );
216 216
217 217 return \esc_url_raw( $url );
218 218 }
219 -
220 -/**
221 - * Get a reaction author's display name as readable plain text.
222 - *
223 - * Shared by the reactions REST route and the block's server render so both produce the
224 - * same value for the same comment: they feed the same Interactivity template, and
225 - * `view.js` swaps the rendered items for the fetched ones wholesale.
226 - *
227 - * This reads the raw column rather than `get_comment_author()`, so it does not pick up
228 - * the emoji rendering that the comment list applies. That is deliberate for a
229 - * plain-text field.
230 - *
231 - * `wp_insert_comment()` callers bypass core's `pre_comment_author_name` chain, so the
232 - * column is not guaranteed tag-free, which is why this cleans rather than just reads.
233 - *
234 - * @since 9.3.0
235 - *
236 - * @param \WP_Comment $comment The comment.
237 - *
238 - * @return string The author name as plain text. May contain `&` as a character,
239 - * so it is safe for a text sink only, never for HTML.
240 - */
241 -function get_reaction_author_name( $comment ) {
242 - // Core stores this column entity-escaped, so decode for the text sinks; stripping after the
243 - // decode is what keeps an encoded tag from coming back to life.
244 - return \wp_strip_all_tags( \html_entity_decode( $comment->comment_author, ENT_QUOTES, 'UTF-8' ) );
245 -}