[wp-trac] [WordPress Trac] #40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code

[WordPress Trac]

#40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code
--------------------------+-----------------------
 Reporter:  dwrippe       |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  4.8.1
Component:  Widgets       |     Version:  4.8
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------

Comment (by FolioVision):

 Replying to [comment:37 synavista]:
 > The best course of action at this point, it would seem, would be to
 admit the error, convert the text editor back to the way it was, and
 simultaneously release the updated HTML Code widget along with a new Rich
 Text Editor. If that is completely impossible, at least figure out a way
 for the TinyMCE Text Editor to both default to the text editor AND
 remember the selected editor type (which I would hope would stop the
 system from stripping out existing content). That makes it a pain in the
 butt for developers to go in and convert to the new HTML Code widget, but
 '''at least it makes it possible.'''

 Great idea.

 Most sensible developers and agencies have not upgraded to 4.8.x yet after
 the debacle of the 4.7.0 and 4.7.1 hacks so doing the right thing now
 would both 1. mean most publishers don't have to deal with this self-
 inflicted wound 2. restore some confidence that the WordPress core team
 still has some interest in actually helping people ''publish'' rather than
 poisoning their lives by breaking their sites with every update.

 @philclothier Your suggestion is also very clear and right on target.

 > Every other CMS I can think of uses two distinct widgets/elements for
 HTML or WYSIWYG. For example Squarespace, Wix and Weebly all do it this
 way, as well as WordPress plugins such as Visual Composer and Beaver
 Builder etc. The best approach, in my opinion, would be to follow this and
 create a dedicated "HTML" widget (which replaces the <4.8 "Text" widget.
 Then create a new widget called "Visual Edtior" which includes TinyMCE.
 When I first saw the announcement of this widget, this is what I assumed
 would be the case.

 Makes a lot more sense to add a useful feature than to destroy an existing
 one and existing websites. If WordPress Core are hell bent on removing the
 text widget (why on earth do that - there is this insanity of wanting to
 bring WordPress to the lowest common denominator, ignoring the existence
 of Typepad, Squarespace, Wix and Weebly who cover this market far, far
 better), then they can deprecate the text widget over the course of 5
 single point releases (i.e. not removing it until 5.4 or so with plenty of
 notice). By then someone could take the time to write a decent migration
 tool.

 @westonruter @afercia @matt @markjaquith @helen

 '''Breaking publishers' websites on updates''' is wrong, anti-productive
 and in the end only '''generates hostility to WordPress'''. It's an own
 goal.

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