[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:
     Type:  defect (bug)                         |  miqrogroove
 Priority:  high                                 |      Status:  assigned
Component:  Shortcodes                           |   Milestone:  Future
 Severity:  blocker                              |  Release
 Keywords:  needs-patch needs-unit-tests 2nd-    |     Version:  3.0.1
  opinion                                        |  Resolution:
                                                 |     Focuses:  javascript
-------------------------------------------------+-------------------------
Changes (by thatguy334233):

 * keywords:  needs-patch needs-unit-tests => needs-patch needs-unit-tests
     2nd-opinion
 * severity:  normal => blocker


Comment:

 This track begins 5 years ago.

 No pressure at all, no urgency, nothing.

 Suddenly, nightly builds are pushed and delivered within 30 hrs before
 release!

 What started (in forums, slack, etc, after peoples started complaining the
 today's update) as:
 "We are looking into that"
 suddenly changed to this:
 https://make.wordpress.org/core/tag/shortcodes/
 (changes to the ShortCode API)

 More or less simultaneously, in forums there are statements that
 "WordPress has disabled the security update from further being installed
 while they address this issue"
 (example: https://wordpress.org/support/topic/wordpress-423-broke-my-
 code?replies=15)

 I see now 2 possibilities:

 Either a BUG was addressed here (and suddenly it was a quiet urgent one,
 if so)
 OR
 a API change has been planned (in advance) and updates where pushed, still
 with a unusual "last minute sprint"

 First option would be acceptable (BUG Addressed),
 ==> but then why was this BUG no issue for 5 years long,
 and suddenly (beneath a time range of 30 hours) it becomes a crucial BUG?

 If second option is true, IMHO
 API Changes *have* to be announced. NO API has ever been receiving such
 crucial changes in just a few hours and then released as a *BUG fix*.

 Please, there are not one, two or 50 sites out there, but K's of sites now
 broken due to this "API UPDATE"

 If it would have been a API UPDATE, every well aware DEV would have been
 prepared, and could have provided compatibility for their Software (or at
 least announce this -future- problem)

 Furthermore, API Updates usually offer backwards-compatiblity.

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