[wp-trac] [WordPress Trac] #15694: Shortcode I/O Intolerant of "]", "<", Quotes, etc.

[WordPress Trac]

#15694: Shortcode I/O Intolerant of "]", "<", Quotes, etc.
------------------------------------------+-----------------------------
 Reporter:  miqrogroove                   |       Owner:  miqrogroove
     Type:  defect (bug)                  |      Status:  assigned
 Priority:  normal                        |   Milestone:  Future Release
Component:  Shortcodes                    |     Version:  3.0.1
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:  javascript
------------------------------------------+-----------------------------

Comment (by chriscct7):

 Replying to [comment:42 jadpm]:
 > Replying to [comment:41 chriscct7]:
 > > > Replying to [comment:38 chriscct7]:
 > > > Replying to [comment:39 jadpm]:
 > > > >  And finally this ticket, while related, is not the changes made
 for 4.2.3, so with that being said, if you would like to talk about the
 4.2.3 issues, the proper venue is the forum on WordPress.org, not here.
 This is an unrelated ticket.
 > > > >
 > > > > Comments 17 to 23 in this very same ticket thread seem to prove
 you completely wrong, sorry.
 > > >
 > > I'm afraid not. Pento and I are both on the team that wrote the 4.2.3
 update portion that dealt with shortcodes. Those commits are related but
 does not deal with the trac ticket they are on. The commits just needed to
 be associated with a trac ticket. If this ticket was for the 4.2.3 release
 it would be tagged for that release. This ticket is not solved yet and is
 currently milestoned for a future release. Also given 4.2.3 is out if this
 ticket was in 4.2.3 it would now be closed with a resolution of fixed.
 It's still open.
 >
 > I am affraid yes. If commits need to be associates with a ticket, then
 tickets holding commits that do not want to get their own ticket for
 obscure reasons must accept comments on the changes they hold. If this is
 a case of "ticket hijacking just for the purpose", we all should be
 entitled to do this same thing.

 Not true at all. Many security commits don't because it would put sites at
 risk by identifying security concerns before sites get a chance to recieve
 the auto updates. Also there's a difference between ticket jacking and
 architectural necessity. Whether or not this ticket is for the 4.2.3 issue
 is not up for debate: its not. Again if you'd like to discuss the changes
 the forum is the most appropriate venue atm.


 > If you think otherwise, I invite you to revert the changes introduced
 here, create a proper ticket for them and slate another point release as
 you wish. Doing otherwise would just mean that an OSS project like
 WordPress can get commits that can not be debated, discussed or even
 commented, which I am sure it not what you mean, right?

 Architecturally to my knowledge that's not possible due to the way it
 works behind the scenes for starters.

 Bottom line: this ticket is for comments on the subject of this ticket
 only, not the 4.2.3 changes. That's not what this ticket is about.

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