Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #40951, comment 151


Ignore:
Timestamp:
07/17/2017 08:53:02 PM (8 years ago)
Author:
Ov3rfly
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #40951, comment 151

    v2 v3  
    1313It is happening now, with a 4.8 updated site and a shortcode which outputs a <ul> with a few <li> and one "commented" <li> which is printed as <p> now, which is bad, very bad, and required code changes within the shortcode PHP-Code. We don't have time to look at any future patches, we have to deal with customers who updated to 4.8 and all their broken widgets at the moment.
    1414
    15 You can't expect any/all WordPress users to (even be able to) transfer all their widgets to other widgets just because somebody had the tiny bad idea to change a "since ever existing" core widget to something else instead of adding a new widget for a completely new feature. People now are upset about WordPress already because their "site looks different" and they "did not do anything" and they have to pay hourly rates to get their sites fixed. Even if they somehow will manage it alone, to copy that "whatever it is" shortcode to a new HTML widget, the shortcode won't even work there, just imagine that disappointment.
     15You can't expect any/all WordPress users to (even be able to) transfer all their widgets to other widgets just because somebody had the tiny bad idea to change a "since ever existing" core widget to something else instead of adding a new widget for a completely new feature. People now are upset about WordPress already because their "site looks different" and they "did not do anything" and they have to pay hourly rates to get their sites fixed. Even if they somehow will manage it alone, to copy that "whatever it is" shortcode to a new HTML widget, the shortcode won't even work there because the widget_text/do_shortcode filter is not there, just imagine that disappointment.
    1616
    1717Sorry about this rant, nothing personal, a real and clean solution would be a complete rollback of "text widget" to pre-4.8 as soon as possible and add a new "tinymce widget" for future use.