WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just completed writing a plugin from another plugin. When I changed the developer name, version and other details from the plugin file, I thought the version tracing would now be done using the new name of the plugin but it actually linked the update to the older plugin until I changed the root folder name for the plugin. Wasn't the update supposed to be happen from the details provided in the file? Please guide. Thanks

share|improve this question
up vote 2 down vote accepted

WordPress uses the 'plug-in slug' to identify a plug-in (and uses this as an 'id' for plug-in updates, though its not clear how, as the code isn't published). The plug-in slug is determined by the location of the .php file header containing the comment header necessary for plug-ins. (see source)

So if your main plug-in file is ...wp-content/plugins/pluginA/pluginA.php your plug-in slug is pluginA/pluginA.php, and will by default check for plug-in updates using that slug.

So to give your plug-in a different slug its necessary to change the name of the plug-in file/directory.

Of course its also possible to just prevent your plug-in from checking for updates or change where it looks (e.g. Have WP Theme update from Git Repository). (This is not allowed for repository-hosted plug-ins).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.