[wp-trac] [WordPress Trac] #50034: Plugin with name conflict is being deleted on scheduled plugins update

[WordPress Trac]

#50034: Plugin with name conflict is being deleted on scheduled plugins update
--------------------------+-----------------------------
 Reporter:  apedog        |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Plugins       |    Version:
 Severity:  major         |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I have a custom plugin configured to update from a github repo.
 Since its creation, another plugin with the same name/slug has been added
 to WordPress plugins repository.

 My plugin is set to auto-update (using Easy Updates Manager). It has no
 recent updates so should remain unchanged.

 However on daily auto-update Cron schedule, the plugin is being deleted.
 And I am unceremoniously greeted with the following error notice:
  **The plugin has been deactivated due to an error: Plugin file does not
 exist.**
 Most probably because of name conflict with the plugin in the WordPress
 repo. At least I assume that's the reason.

 Possible fix: Introduce a plugin header field telling WP to never
 associate the plugin with the WP.org plugins repo. This should work
 whether plugin is activated or not. ie. without requiring the plugin
 itself to hook into WordPress core functionality to avert its deletion.
 {{{
  * WordPress Repository: false
 }}}
 Or some other more elegant naming convention. Like:
 {{{
  * Plugin Repository: github.com | wordpress.org
 }}}
 The later would even be more extensible.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50034>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform