Support » Plugin: Custom Post Links » Nice fork! Minor problem: plugin name conflict

  • Resolved Jonathan Daggerhart


    Hi grosbouff,

    Just wanted to say that I think it’s pretty cool what you’ve done here in recreating the plugin. I checked out your code and really like your approach to using the core “link” type as a library of links that are then referenced by individual posts. Great job!

    One minor issue is due to the plugin having the same exact same folder name. Now my sites are asking my to upgrade to your version of the plugin. Which would be fine if they were more similar, but I don’t see a clear upgrade path.

    This support ticket is just to let you know that I will change my github project name, since that is probably easier than you getting a new repo for your fork. This means the url and plugin folder name for my version of the project will change (for your documentation). I don’t think this will inconvenience anyone, considering the github project has zero stars. Just wanted to give you a heads up in case you get any random support requests from old-project users about the plugin being “broken” after updating to 2.0.

    That’s all, I’ll Let you know when I get around to changing the original repo name.

    Good luck with your fork!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author grosbouff


    Hi @daggerhart, and thanks for your nice feedback (and plugin) !

    You’re right, it would be easier (for me) that the github project change its name rather than the WP plugin repo.

    BUT if you like, I COULD make an upgrade function to switch from your version to mine. Should take me one hour or two, no more.
    Let me know if you would want that. We could even merge the project then.


    Plugin Author grosbouff


    Well @daggerhart;

    I did implement the upgrade function. Enjoy ?

    Very cool! I will give it a shot in the next couple of days (when I find a moment) and let you know how it goes.

    Thanks again!

    This looks pretty good to me. I did a simple test, and it worked as expected.

    Going forward, I’d like to clean up the repos a little more. I can’t fork your repo and contribute to it, because it is already a fork of mine (github won’t let me).

    I’ve already merged your changes back into my repo (the “base” repo) — see here

    What do you think of this idea?:

    You delete your fork, and I will transfer the original repo to you. Then you will have the “real”/base repo, and I can fork it and submit pull requests to you.

    Alternatively, I can add you as a contributor to the base repo. Whatever you think is best. Personally, I’d prefer to transfer it to you, as I don’t really have time to support the plugin on


    Plugin Author grosbouff


    Ok Jonathan, it seems OK to me.
    I deleted the Github repo…

    Thanks !


    Awesome, repo transfer started! Looking forward to updates, and contributing back to this when possible.

    Thanks again!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Nice fork! Minor problem: plugin name conflict’ is closed to new replies.