[wp-trac] [WordPress Trac] #40907: Introduce widget dedicated for HTML code

[WordPress Trac]

#40907: Introduce widget dedicated for HTML code
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
     Type:  feature request                      |  westonruter
 Priority:  normal                               |      Status:  reopened
Component:  Widgets                              |   Milestone:  4.8.1
 Severity:  normal                               |     Version:  4.8
 Keywords:  has-patch has-unit-tests commit      |  Resolution:
  fixed-major                                    |     Focuses:
-------------------------------------------------+-------------------------

Comment (by FolioVision):

 I've been thinking hard about this as well @slewisma. The proposed
 solution by westonruter is really a half measure and inadequate. The only
 viable solution would be to add an HTML widget and leave the text widget
 alone. Apparently Matt doesn't want to do that (I'm not in the Slack
 conversation about it but that's what's reported). Matt summoned quora in
 Slack and pronounced an edict - this is not democratic in any shape or
 form. It doesn't serve the project or its existing users.

 Matt wants this as it would suit WordPress.com and the strange grasping
 for low-end marketshare (people who aren't competent to manage websites or
 hosting and have no business having a self-hosted WordPress, Drupal,
 Joomla install - these users should be on WordPress.com, Typepad,
 SquareSpace or Tumblr - Medium would be too complex for them). These "new
 users" will just poison the WordPress ecosphere with absurd support
 demands and soil the project's reputation with complaints about broken
 sites). Our only hope is that they won't be able to find WordPress.org or
 use the plugin directory at all (otherwise every plugin created for a user
 with an IQ above room temperature will quickly slide to a 2 rating).

 There seems to be very little respect among the current WordPress core
 team (it seems to me a voting majority are directly on the Automattic
 payroll) for mid-tier Wordpress users and agencies. Agencies and
 developers who have built the WordPress project and created the ecosphere
 from which Automattic now profits.

 This makes users and agencies very angry, Matt. If your goal is to
 diminish the reputation of the WordPress project and continue to make
 agencies lives a misery by 1. too frequent updates 2. no real improvements
 (target areas could include performance, stability, security holes, native
 comments, native caching) 3. breaking updates, keep on trucking.

 I've written you privately that there's no sin in making a mistake but
 there is a great sin in persisting in it.

 What's needed here is to **add an html widget** and **leave the text
 widget alone**. There's no good reason to break WordPress yet again,
 particularly after the debacle of WordPress 4.7.x. Those (foolish) early
 adopters who may already have broken widgets from too early upgrade to
 WordPress 4.8 should get some kind of compromise solution like the one
 Westron has worked so hard on (remigrating their widgets back to text
 after they've fought through the issues) wouldn't be fair either.

 Those of you who are looking for a way to discreetly postpone these issues
 can use [https://wordpress.org/plugins/businesspress/ BusinessPress] to
 stay on WordPress 4.6.x or WordPress 4.7.x with security updates until
 there's finally a drop-in solution. What a tremendous waste of everyone's
 time this misstep is.

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