[wp-trac] [WordPress Trac] #58366: Shortcode Support Regained but Content Filters are messing with Shortcode HTML

WordPress Trac noreply at wordpress.org
Wed May 14 12:32:31 UTC 2025


#58366: Shortcode Support Regained but Content Filters are messing with Shortcode
HTML
-------------------------------------------------+-------------------------
 Reporter:  domainsupport                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Shortcodes                           |     Version:  6.2.2
 Severity:  normal                               |  Resolution:
 Keywords:  has-test-info needs-unit-tests has-  |     Focuses:
  patch dev-feedback                             |
-------------------------------------------------+-------------------------

Comment (by SirLouen):

 Replying to [comment:95 kubiq]:
 > Hello @SirLouen ,
 >
 > I'm testing the patch 58366-poc.2.diff and here is my observation:
 >
 > [[Image(https://img.kubiq.sk/2025-05-14_09-06-36.png)]]
 >
 > Let's say there are **2 major facts** that we need to know about each
 shortcode:
 > 1. **Where** it is placed ( template, template part, post content )
 > 2. **How** it is placed ( inline in paragraph as part of the text,
 Shortcode block, Custom HTML block, ... )
 >
 > And there are these problems:
 > 1. Using shortcode in **Shortcode Block** in **Template or Template
 part** will lead to extra `<p>` wrapper as it is highlighted on my
 screenshot
 > 2. Using shortcode in **any form** inside the **Reusable block** that is
 placed **in Template or Template part** will completely ignore the
 shortcode and it will just render raw `[xxx]`

 I have not tested that part because I'm not confident that not showing the
 contents in Reusable block is part of this report.
 This is probably happening because of the security hindrances to avoid
 executing shortcodes just anywhere.
 I think it's more appropriate to open just a new ticket for this specific
 scenario and leave this report just for the HTML issues part.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58366#comment:96>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list