[wp-trac] [WordPress Trac] #31138: Backup of a plugin / theme directory.

WordPress Trac noreply at wordpress.org
Fri Jan 30 18:32:51 UTC 2015


#31138: Backup of a plugin / theme directory.
-----------------------------+------------------------------
 Reporter:  aercolino        |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  4.1
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------------------

Comment (by lgladdy):

 I saw your post on #29820 and figured it made more sense to reply here.

 I'm actually against this from a mentality point of view. I think a better
 question is should the editors carry better warnings about those changes
 being lost when upgrades occur.

 Plugin and theme updates can often be for security reasons and critical -
 you don't want users to be able to go back to a vulnerable version, even
 if that means losing changes (that they should be aware won't stick
 around)

 Every time I've wanted to change a plugin, i've made a copy and appended
 something to the name to stop it auto-updating - thus taking on
 responsibility for maintaining it. I deploy sites to production with
 disable_file_mods to prevent the editors working.

 People should be backing things up, either manually, through their host or
 through a service like vaultpress, as is recommended anyway!

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


More information about the wp-trac mailing list