Title: Forking A WP Plugin
Last modified: August 22, 2016

---

# Forking A WP Plugin

 *  [Host Magi](https://wordpress.org/support/users/mandraagora/)
 * (@mandraagora)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/forking-a-wp-plugin/)
 * Hi!
    I have a plugin that I want to fork and create my own version. I know the
   that I can do this under the terms of the GPL, what I do not know is how. Here
   are my main questions: 1. The plugin requires activation which sends the user
   through the original developers system. How can i remove the activation feature
   altogether, as my version will not require this? 2. In which files should I look
   for links/references to the original developer so I can add my own details and
   change it to say that the new plugin is based on “XXXX”?

Viewing 1 replies (of 1 total)

 *  Thread Starter [Host Magi](https://wordpress.org/support/users/mandraagora/)
 * (@mandraagora)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/forking-a-wp-plugin/#post-5625957)
 * Ok, so I have managed to make all of the name changes, edit references to the
   original developer, etc. Now I am just hasving some trouble trying to figure 
   out how to completely remove the Activation api. I tried renaming the api files,
   but that resulted in blank white screen on my development site admin area when
   I loaded the plugin.
    Any thoughts on how to figure this out?

Viewing 1 replies (of 1 total)

The topic ‘Forking A WP Plugin’ is closed to new replies.

## Tags

 * [developing](https://wordpress.org/support/topic-tag/developing/)
 * [forking](https://wordpress.org/support/topic-tag/forking/)

 * 1 reply
 * 1 participant
 * Last reply from: [Host Magi](https://wordpress.org/support/users/mandraagora/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/forking-a-wp-plugin/#post-5625957)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics