The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
modification graveyard problem! gettin real annoyed now
im getting sick of the graveyard thing now...
having a lot of mods installed on my forum, like most users, we tend to try and keep up with newer mods that come out, and like to remove/uninstall previous mods that are either out dated or moved to the graveyard, BUT what if we dont have the original zip file install any longer? well i wouldnt know what files to delete or templates to edit if i cant GET the ORIGINAL file now would i? and if the releasing modder is not answering pm's, what am i suppose to just accept that? NO! we all know removing a mod by uninstalling it with the plugin isnt always the only way to go, so vb.org needs to come up with a better way of managing mods being dumped in the graveyard. my suggestion: if a mod is being moved to the graveyard and there are users that have it installed, be a little bit more courteous and before closing the mod out, reply to the mod thread and give DETAILS ON WHAT EXACTLY NEEDS TO BE DONE TO REMOVE THE MOD!!!the reverse of the install directions would be a nice thing to read once in a while incase we dont have the original files or zip file or whatever we might have had to install the thing. so posting the files needed for deleting, template edits needed for removal, and the plugin needed to be removed would be REAL helpful for us forum admins trying to stay up to date with current releases. |
#2
|
|||
|
|||
Yes it would be nice if the authors left uninstall instructions. But you would be in the same problem if you had installed an older version of a modification that have been overwritten with new versions.
Bottom line is that you are yourself responsible to keep the documentation (and if needed install files) secured on your own PC or elsewhere. You can never trust that something you once downloaded anywhere on the internet to be available forever. |
#3
|
|||
|
|||
Quote:
its not about responsibility to keep records. stuff happens like accidental deletes, viruses, crashes of hard drives, so on. and we rely on the data here sometimes to guide us back. its not about having the authors leave instructions on uninstall, its about the person moving a mod with installed users to the graveyard and putting the uninstall procedure in the first post so the installed users can remove the thing on their end JUST IN CASE the file is deleted from the installed users side. its common courtesy and a procedure that should be implemented here without question or argument. |
#4
|
|||
|
|||
Modifictions are mostly moved to the graveyard because the author wants to to have it deleted, mostly author already removed any files, so in most cases staff can not do anything.
|
#5
|
|||
|
|||
yes i found this out, why i have this post here: https://vborg.vbsupport.ru/showthrea...66#post1752066
i know modders do request it to be junked, but there are mods ive had installed that were dumped by staff, and i had to contact the modder by pm and wait days to get a response and not always get the info i needed, and it made everything harder. this option i am submitting is one that should be implemented if a mod is placed in the graveyard. if its by request of the author, than you guys should make the author detail the uninstall procedure before the files are dumped. maybe changing permissions allowing original authors to delete their zip files here, i dunno. however it works, but its something that needs to be done. im sure there are alot more posts and concerns about this kind of issue on here. |
#6
|
|||
|
|||
actually i answered you request for support on this hack.
most of the few maniacs here have all versions of all hacks released here, just wait a little so you can have support on these old graved stuff... what you suggest was already debated, but due to the fact that all the releases here are applyed of the same copyright, the authors really have to give-over the products to someone else if you want support and followup... making them abandonware would change things, but it's not in the logic of a commercial product. |
#7
|
||||
|
||||
As Marco said, almost all mods go in the GY for one of two reasons.
1. Author request. 2. Security Issue. I would say that well over 90% are for reason 1, and in most cases (like the mod you mention), the files have already been deleted. It is not the job of staff to inspect every modification that is moved, see how its installed etc, and then provide uninstall instructions (even if we could). |
#8
|
||||
|
||||
I agree with Gotti. I've had this issue a few times. It doesn't kill for the author to leave a note why it was moved to the GY and how to uninstall it, while keeping the original downloads there. There is no harm in doing this.
|
#9
|
|||
|
|||
the problem is not the note, it's the author's choice to give no note.... you can't control everybody's mind in that topic...
|
#10
|
||||
|
||||
It would be nice if the author would post the uninstall instructions prior to deleting the product, but in every case where I have moved a mod to the graveyard due to the product being deleted, there has been no note left by the author at all.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|