[wp-trac] [WordPress Trac] #40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code
WordPress Trac
noreply at wordpress.org
Mon Jul 17 08:55:27 UTC 2017
#40951: New Text Widget - Switching Between Visual/Text Editor Strips Out Code
-------------------------------------------------+-------------------------
Reporter: dwrippe | Owner:
Type: defect (bug) | westonruter
Priority: normal | Status: reopened
Component: Widgets | Milestone: 4.8.1
Severity: major | Version: 4.8
Keywords: needs-testing has-unit-tests has- | Resolution:
patch commit fixed-major | Focuses:
-------------------------------------------------+-------------------------
Comment (by bobbingwide):
Replying to [comment:138 westonruter]:
> > 4. The message doesn't go away even when the widget has been changed.
> > So perhaps the message should say 'This widget may contain code...'.
>
> Good point. Or even, “This widget ''may have'' contained code”.
@melchoyce thoughts?
>
Is there any reason why legacy mode has to be permanent?
Some widgets could become legacy simply because of a new line at the end
of the text.
Removal of that new line would allow use of the visual editor.
And conversely, any reason why $instance['filter'] = 'content' is also
permanent?
A flexible approach would allow a user to switch to text only while still
giving the option of wpautop processing.
It may also cater for users who upgraded to 4.8 and now have problematic
widgets.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40951#comment:141>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list