[wp-trac] [WordPress Trac] #10082: shortcode bug
WordPress Trac
wp-trac at lists.automattic.com
Mon Jul 27 02:12:54 UTC 2009
#10082: shortcode bug
-------------------------------+--------------------------------------------
Reporter: Denis-de-Bernardy | Owner: petervanderdoes
Type: defect (bug) | Status: accepted
Priority: normal | Milestone: 2.8.3
Component: Shortcodes | Version: 2.8
Severity: critical | Keywords: has-patch
-------------------------------+--------------------------------------------
Comment(by godfreykfc):
If we are supporting nested shortcode, then we'll have to deal with
situations like these:
{{{
[shortcode]
[shortcode]...[/shortcode]
}}}
If nesting is not supported, then this should clearly be interpreted as an
(implied) self-closing {{{[shortcode /]}}} followed by a
{{{[shortcode]...[/shortcode]}}}. However, if nesting is permitted, then
it can also be interpreted as {{{[shortcode] [/shortcode]}}} pair wrapping
around the content {{{[shortcode /]...}}}. IMO, either interpretation is
fine, but it should be clearly defined (and test cases should be written)
and we should make sure that interpretation won't change from
implementation to implementation. We should also deprecate the implied
self-closing syntax and encourage people to start using the explict
{{{[shortcode /]}}} syntax to avoid ambiguity.
By the way, as pointed out in #10473, this is not working in the current
release at all, so please make sure it is fixed by the submitted patch.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10082#comment:31>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list