[wp-trac] [WordPress Trac] #31779: Warn users before using a built-in file editor for the first time

[WordPress Trac]

#31779: Warn users before using a built-in file editor for the first time
--------------------------------------+---------------------------------
 Reporter:  helen                     |       Owner:  helen
     Type:  enhancement               |      Status:  reviewing
 Priority:  normal                    |   Milestone:  4.9
Component:  Themes                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:  ui, administration
--------------------------------------+---------------------------------

Comment (by boogah):

 Replying to [comment:55 melchoyce]:
 > Okay... here's what I'm thinking :)
 >
 > When you first visit either `theme-editor.php` or `plugin-editor.php`,
 you see [attachment:WF - Interstitial.png], which warns you about the code
 editors and makes you write "I understand" to proceed. Once you do this,
 your user never sees it again.
 >
 > If we want to present additional warnings, we can frame them as "tips."
 See [attachment:WF - CSS Warning.png] for an example. These tips will be
 dismissible notifications that only appear once. Once you dismiss them,
 they're gone.
 >
 > Does this seem reasonable?

 I really like this, Mel. Great job! The "I understand" prompt is a good
 way to make sure that people don't blindly stab at the "Proceed" button to
 bypass the warning.

 I think doing this once for `theme-editor.php` and once for `plugin-
 editor.php` would be great though as the plugin prompt should (probably)
 warn that their changes may be overwritten by a future update to the
 plugin and the theme prompt should push folks to the concept of child
 themes.

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