Title: Forking a Plugin
Last modified: August 21, 2016

---

# Forking a Plugin

 *  Resolved [mythusmage](https://wordpress.org/support/users/mythusmage/)
 * (@mythusmage)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/forking-a-plugin/)
 * Name: WikiPress
    Fork of: WPW!=S
 * Changes: Delete sections (please instruct); add page order (please instruct)
 * I figure, sections aren’t really necessary, just make the top level pages the
   sections.
 * In addition, it turns out I’m having a problem with the custom page order plugin.
 * [https://wordpress.org/plugins/wordpress-wiki-that-doesnt-suck/](https://wordpress.org/plugins/wordpress-wiki-that-doesnt-suck/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Chris Reynolds](https://wordpress.org/support/users/jazzs3quence/)
 * (@jazzs3quence)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/forking-a-plugin/#post-5125586)
 * First, you’ll need to give it a different name. A plugin named WikiPress already
   exists: [http://wordpress.org/plugins/wikipress/](http://wordpress.org/plugins/wikipress/)
 * This means that if you are going to upload it to wp.org, you’ll need to give 
   your plugin a unique name to prevent clashes with the existing plugin and, additionally,
   if you kept the name anyway (bc you weren’t going to distribute it), you’d still
   need to at least make the version greater than the version of the existing plugin,
   otherwise WordPress will think there’s an update available and overwrite your
   version with the one from WordPress.org with the same name.
 * Sections are simply taxonomies. So all you need to do to remove those is to not
   register the taxonomy. As I said in the [other thread](http://wordpress.org/support/topic/time-to-update-1?replies=16#post-5797272),
   I had no problem converting posts from one post type to another post type, so
   that sounds to me like it has to do with your environment. However, if you’re
   registering the post type as something other than wpwtds_article, it _might_ 
   make a small amount of difference with regards to the convert post types plugin.
   Otherwise, you’ll need to convert your posts programmatically (which you could
   probably see how it’s done by looking at the code in [Stephanie Leary’s plugin](https://wordpress.org/plugins/convert-post-types/)).
 *  Thread Starter [mythusmage](https://wordpress.org/support/users/mythusmage/)
 * (@mythusmage)
 * [11 years, 10 months ago](https://wordpress.org/support/topic/forking-a-plugin/#post-5125803)
 * Turns out WikiPress has been abandoned.
 * I know have a copy of Professional WordPress Plugin Development; I’ll study it
   and see about correcting, updating, and expanding WikiPress, then releasing it
   under WikiPress Revived.
 * Any advice?
 *  Plugin Author [Chris Reynolds](https://wordpress.org/support/users/jazzs3quence/)
 * (@jazzs3quence)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/forking-a-plugin/#post-5125883)
 * Lots, but none better than you’ll get in Pro WP Plugin Development 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

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

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-wiki-that-doesnt-suck_c2adac.
   svg)
 * [WordPress Wiki That Doesn't Suck](https://wordpress.org/plugins/wordpress-wiki-that-doesnt-suck/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-wiki-that-doesnt-suck/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-wiki-that-doesnt-suck/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-wiki-that-doesnt-suck/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-wiki-that-doesnt-suck/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-wiki-that-doesnt-suck/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Chris Reynolds](https://wordpress.org/support/users/jazzs3quence/)
 * Last activity: [11 years, 9 months ago](https://wordpress.org/support/topic/forking-a-plugin/#post-5125883)
 * Status: resolved