WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #23318, comment 8


Ignore:
Timestamp:
06/27/2014 08:22:27 PM (5 years ago)
Author:
DavidAnderson
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23318, comment 8

    initial v1  
    66I'm not yet seeing, though, why WP needs to know the exact ID of a plugin as distinct from its slug. If the plugin is from the wordpress.org repository, then WP identifies it through the slug... if the slug has been changed, then updating it with a pristine version (i.e. unchanged slug) is probably a terrible idea.... on the other hand, if the slug is *not* from the wordpress.org repository, then it's in 3rd party territory anyway and the developer can implement whatever mechanism he pleases for identifying the plugin (i.e. it's not a problem that core needs to solve).
    77
    8 I think I'm really saying that 1) I agree with crazycoders in #4 - the slug is the identifier, and if you decided to change/break it, then you should have no expectation that anything else will work any more than if you decide to replace "<?php" with "<?squirrels!" everywhere. 2) I think it's best just to focus on the "plugin info fetched from the wrong remote service" problem.
     8I think I'm really saying that 1) I agree with crazycoders in comment 4 - the slug is the identifier, and if you decided to change/break it, then you should have no expectation that anything else will work any more than if you decide to replace "<?php" with "<?squirrels!" everywhere. 2) I think it's best just to focus on the "plugin info fetched from the wrong remote service" problem.