Changes between Initial Version and Version 1 of Ticket #40907, comment 49
- Timestamp:
- 06/27/2017 08:41:30 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #40907, comment 49
initial v1 1 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.1 I've been thinking hard about this as well @slewisma. The proposed solution by westonruter is really a half measure and inadequate (thank you again for your hard work, Weston, you've done your best with an impossible brief). 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. 2 2 3 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).3 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). 4 4 5 5 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. … … 9 9 I've written you privately that there's no sin in making a mistake but there is a great sin in persisting in it. 10 10 11 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.11 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 security 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 Weston has worked so hard on (remigrating their widgets back to text after they've fought through the issues) wouldn't be fair either. 12 12 13 13 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.