Plugins stay in "Build" when deleted

[Shorty]

So a minute ago, I deleted a plug in I made from the manage tab. It also deleted it from the Build tab. I think it should have just deleted the one in the Manage tab. I personally wouldn't want all my plug ins in my manage tab if I will never use them. So either that, or at least a way to get them back.

[VS Admin]

Thanks for your input. Maybe we could make the deletion message more clear; however we will not be able to 'unlink' the pages from each other.

[Ryan Roos]

We will definitely improve the delete message like Patrick said. Remember that you are able to disable (turn off) plugins that you aren't using (the checkbox to the left, on the manage page). So if you don't want them removed from your forum but you also don't want them active simply turn them off. We specifically added that functionality for this purpose.

[Shorty]

Ah alright. Then if say you did do delete it. Is there any way to get that plugin back into the build section so if you need to you can edit it. Also, can you only edit the plug ins you built on the forum you made it on?

[Ryan Roos]

If you delete something then it's gone. That's why you are prompted with a dialog asking if you are sure you want to delete things. In certain places where it's very important we even have you type the word 'delete' before you can delete things. Unless you exported a copy you can't recover deleted things. As we said, in the case of Plugins we will make it more clear that you are, in fact, deleting the plugin from your forum completely. We already added the update to our to do list this morning.

When you export a plugin you need to select if it's editable or not. There is a yes/no option. If yes is selected then anyone can edit the source of the plugin in the build page. If no is selected then the plugin is only for use on the manage page.

This allows authors to share plugins during development, but then lock the code away once they are done. That way people can't steal their code. Plugins that aren't editable are meant to be installed and used by others through the user interface, not edited at the source.

This is why we are so excited for plugins. Right now in v4 non-coders are forced to deal with code in the headers and footers. In v5 non-coders can simply install existing plugins and never need to see code at all. They can use the user interface. Coders still can make complex mods without the worry of people stealing or breaking their codes. Or if they want they can leave plugins editable and place a license if they wish. What I'm witnessing already is non-coders trying to make plugins. That's still the header and footer mentality. It's great if people want to try to learn the plugin system and modify their forums. I encourage that learning. More plugins for everyone. But ideally non-coders should be requesting plugins and installing them from the user side. Not trying to author every code they can into their own unique plugin that's only going to be on their forum. That's not quite what a plugin is. That's what headers and footers are still for. Of course plugins do have the advantage of permissions and on/off switches so feel free to make plugins just for yourself if you like. Just be aware that the Plugin Library is intended to be a collection of ready made mods for people to share, use and rate.

[Shorty]

Ah. Alright. Thanks for that!