How to remove plugin #88

Open
STAR-ZERO opened this Issue Jan 17, 2013 · 39 comments
@STAR-ZERO

I want to remove the plugin. I do not find a way to remove plugin.

@gnarf

We need to document this, but basically you'll need to email plugins@jquery.com.

@ajpiano

I think we need something better than that. What do those of us who receive e-mail at plugins@jquery.com do to remove the plugin then?

@gnarf

The administrative process is also missing, so we can develop that here. I'm sure @scottgonzalez has some magic delete it from the database based solution. No matter what though, to the end user, its basically email us right?

@ajpiano

I think that we should probably find some way to automate it...otherwise it's yet another manual process to stay on top of...

@STAR-ZERO

I think need remove plugin automate if remove the GitHub repository.

@ajpiano

Requiring someone to remove the repository from GitHub seems like a not-good thing to require, and furthermore I don't believe it fires any hooks

@ajpiano

By the way, what plugin do you want to remove @STAR-ZERO ?

@craigmdennis

I am in the same position. Errors while getting my plugin to show up in the registry means the plugin page no longer reflects the GitHub repo. Mismatched tags leading to 404s etc.

It would be ideal to be able to delete the plugin entry from the registry and start again.

Alternatively (or maybe in addition) it would be nice if the registry was somehow able to re-check the tags and update itself on the post-receive hook. This would solve my issues (and possible @STAR-ZERO's) but I doubt it would eliminate the need for a 'remove' feature.

@scottgonzalez

Just to make sure everyone is clear on this: No matter what happens, you should not delete and re-create a tag that you have already published.

@craigmdennis

Yes, that makes sense. Would a 'remove' function enable us to 'start fresh'? I agree it doesn't make sense to tie it directly to a GitHub repo deletion.

@ghost

What happens when a tag is deleted? Currently, it seems to be leaving a ghost version in the plugin's page.

@scottgonzalez

What happens when a tag is deleted? Currently, it seems to be leaving a ghost version in the plugin's page.

You should never delete a tag that has been made public.

@ghost

It may be true that I "should never delete a tag that has been made public", but the question is how the plugins site handles someone doing this when it happens.

@scottgonzalez

@gidyn It seems like you already know what happens: the plugins site does nothing. There is no process for removing a plugin right now.

@rygine

@scottgonzalez pointed me in this direction.

please remove this duplicate entry in the repository:
http://plugins.jquery.com/cyclejs/
it references version 1.0.4

if more information is needed, please let me know. thanks!

@localpcguy

Was just looking for a way to remove a plugin. I renamed a plugin, and now it shows up under both names. I considered adding a "blank" (but valid) manifest file to the old plugin name repo (I setup a new empty repo with a link to the new one) but ideally there would be some way to delete it.

What about a key in the manifest file? It might be a little yucky for the user flow, but there could be a "removePlugin" key in the manifest file that is optional, and if true, deletes it from the plugins.jquery.com site. Or maybe an optional "expiresOn" date, that if it is past that date, the plugin no longer appears in the registry.

Just spit-balling a few ideas, ideally it would remove on repo-deletion as well, but you shouldn't have to delete your repo just to remove it from the plugins registry.

@scottgonzalez

What about a key in the manifest file?

It would be horrible to ask people to add code and create a tag. That's the opposite of what they want to do. It also in no way addresses the situation of wanting to remove a single version.

Or maybe an optional "expiresOn" date

Why would you ever want your plugin to expire?

...you shouldn't have to delete your repo just to remove it from the plugins registry.

Obviously.

@localpcguy

Just to make sure everyone is clear on this: No matter what happens, you should not delete and re-create a tag that you have already published.

Does deleting a tag send a notification? That may be a good way to remove a single version (question is would the registry fall back to the previous version then? What would be the expected behavior?)

It would be horrible to ask people to add code and create a tag.

I agree, that's why I mentioned it would suck for the user flow. Again, just brainstorming cause ideas might cause other people to think of something they may not have.

@rygine

I had to change the name of my plugin as it was conflicting with another. Please remove the following entries:

http://plugins.jquery.com/cycle/
http://plugins.jquery.com/cyclejs/ (duplicate)

Thanks!

@GregDThomas

Hi, please can you remove the following erroneously created plugin;

http://plugins.jquery.com/jquery-localtime/

Thanks,

Greg

@DmitryFillo

Hi!

I'm maintainer of http://plugins.jquery.com/filloviewport/
Name of this plugin has been changed (https://github.com/DmitryPhilimonov/jquery.porthole) and links are points to nonexistent repo now. Please, delete this node.

Sincerely, Dmitry.

@scottgonzalez

Remove the duplicate viewport 0.2.3 release created from the v0.2.3 tag (see #133).

@jasonalvis

Hello,

I have created a plugin called showmore and renamed it to show-more

Could you please keep: http://plugins.jquery.com/show-more/
Could you please delete: http://plugins.jquery.com/showmore/

Thank You,
Jason

@greenish

Hi,

I renamed my plugin from "greenishSlides" to just "Slides": http://plugins.jquery.com/slides/
Could you please remove the registry entry for "greenishSlides": http://plugins.jquery.com/greenishSlides/

Thanks a lot

Philipp

@ahsteele

Please remove version 0.1.0 from http://plugins.jquery.com/chord/. Thank you.

@romanglom

Please remove this plugin http://plugins.jquery.com/myplaces/
I'll publish it again with the correct conditions.
Thanks

@konsultaner

Please remove this plugin http://plugins.jquery.com/jsSimpleSlider/
I named it wrong

@borisdamevin

Please remove this plugin: http://plugins.jquery.com/lightbox/
It no longer exists.
Thank you.

@arvgta

please remove this one, too : http://plugins.jquery.com/history/ (all versions)

Thanks!

@scottgonzalez

Remove cycle 1.0.3, 1.0.5, 1.0.6, 1.1.0 (published by someone prior to @malsup).

@filipdbrsk

Hi, I am the creator of http://plugins.jquery.com/imapping/. Can you please remove this plugin for me? I already removed the git repository. The plugin will be back later, enriched with more features.
Thank you! :-)

@filipdbrsk

I just checked, my plugin page is still alive. Can you please remove it?

@scottgonzalez

Plugins can't currently be removed. That's why this issue exists.

@shabeer-ali-m

http://plugins.jquery.com/jput/ please remove version 1.0.1

@johngrogg

Please remove http://plugins.jquery.com/freshrealm-oauth-2/
it was a duplicate, which I'm not sure how it got created.

@harishuw

Hi

i have a plugin
http://plugins.jquery.com/jformslider/

when i updated with a new version
i can see two sliders

in below link
http://plugins.jquery.com/tag/jformslider/

i can see two plugin
http://plugins.jquery.com/jformslider/
http://plugins.jquery.com/jformslider-2/

how can i remove duplicate?

@balachuang

I created a new plugin but type a wrong name. I change the plugin's name in manifest file, a new plugin with correct name is created but the old plugin with wrong name is still there. Could you please to help me to remove the original plugin, thanks.

Here is the information of the plugin to be remove:

Name:  imagesLoaded 

Author: Bala Chuang

Description: A simple jQuery Icon Picker plugin.

@arnaudleyder

Hi, can you please remove http://plugins.jquery.com/magneticmediajs/? I am the creator of the plugin and I am releasing a new version which still uses jQuery but is not available as a plugin anymore. Guys you have to provide a way for removing plugins I am pretty sure it violates privacy laws in Europe not being able to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment