[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:  Awaiting Review
Component:  Themes                      |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  good-first-bug needs-patch  |     Focuses:  ui, administration
----------------------------------------+---------------------------------
Changes (by helen):

 * keywords:  good-first-bug has-patch needs-testing => good-first-bug
     needs-patch


Comment:

 Replying to [comment:24 brocheafoin]:
 > Does this mean this task is blessed for 4.7?
 >
 > Can we work on the wording right here or do we have to submit patches?

 I generally don't move existing tickets into a milestone without a patch,
 but so long as there's general agreement that this is a good move and
 patches are made, I imagine it would go into 4.7.

 Language work can go on right here on Trac, it can be annoying to do via
 constant repatching.

 Replying to [comment:25 boogah]:
 > It'd be nice to have the ability to not hide the interstitial after it
 has been dismissed though. Via a filter, perhaps?

 I guess there are two potential methods here, one that is kind of hacky
 but not adding new hooks, and the other new hooks. I suppose a new hook
 makes sense in particular for managed instances and hosts - curious if in
 those cases you'd want to be linking off to your own resource instead of
 .org.

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