The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
[Suggestion] Re: Reason For Graveyarding
This is just a simple suggestion - I'm not sure if it has been made before, probably has IDK... But I think it's an important suggestion. Within my forum communities - I've always valued the concept of keeping everybody in the know - so this is what my "Modification Graveyard" suggestion is all about: transparency and keeping Members in the know.
So... I just visited the following thread: https://vborg.vbsupport.ru/showthread.php?t=220517 ==> 1 post having nothing to do with the closed, graveyarded thread... I've seen rather many posts very similar and it simply gets on my last nerve, seeing ditched threads with no explanation as to what the issue is. It especially drives me nuts when a modification I've actually downloaded and installed on my board has been sent to the graveyard... Suggest: For each graveyarded thread - Whenever the thread is graveyarded or whatever it's called - the vB.org Staff Member who closed the thread enters into a formfield (at time of closure of course) a brief description of why the thread has been locked, closed, graveyarded, given to the spirit realm, whatever.... That brief description should then show for all registered & licensed Members somewhere within the original post. I'm sure it's a relatively easy modification to accomplish this suggestion. I think giving a bit of information to us regular folks (read: registered and licensed vBulletin customers who care about the modifications shared in this community) can only go to show that there is a bit of respect on part of the vB.org Staff Members given to us who are interested in knowing why a modification has been swiped away and given no further download priviledge. At bare minimum - some consideration/explanation should be given to those who have downloaded/installed the modification. Thanks, Jacquii. |
#2
|
||||
|
||||
A reason is posted in the thread (visible to staff only) and also sent to the mods Author.
The only time it is really any concern of anyone else is if its been quarantined due to a security issue, in which case the standard precedure includes contacting all members who have downloaded it and/or marked it as installed. JFYI, excluding security issues, almost all GY mods are either due to author request, or because they no longer have files attached. |
#3
|
||||
|
||||
Ah - okay - I've just been concerned a few times with trying to delete a modification completely - especially recently after new server migration - and a couple mods had been graveyarded. I had to seek other means to download the mod to see what files needed to be deleted and such... It would be a good idea perhaps that if the mod is still available that it can be downloaded at least to find out the correct uninstall procedure.
Jacquii. |
#4
|
||||
|
||||
The basic point of a mod being in the GY is that it is no longer available for download.
In the past they were simply removed from public view entirely, the GY was created so that the thread would still be visible, without the mod actually being downloadable anymore. |
#5
|
||||
|
||||
I know - but that still kinda leaves the people who've downloaded/installed who actually want to totally remove the modification (especially if there's a vulnerability) up s**t creek with no paddle. I like the idea of at least having a paddle with which to row if I'm up s**t creek.
Jacquii. |
#6
|
||||
|
||||
Ideally, uninstall instructions, or at least a list of all files uploaded or edited along with database changes, would be listed in the first post. That way those instructions would always be available. Unfortunately, we can't make the mod continue to be available for download since that defeats the purpose of removing the modification.
|
#7
|
||||
|
||||
Why don't we all screw our heads on and use a little common sense. We don't allow the files to be downloaded but allow the txt file with the uninstall instructions to be downloaded so that any security issues can be acted upon and dealt with by the people who have the script installed.
It's easy to say that the instructions are in the first post but this is not always the case they are usually in the txt doc. What your basically doing is sending an email out alerting of an exploit, security issue but not giving the info to the person to uninstall the script and files. Just a suggestion, I haven't made one of those for a while. |
#8
|
||||
|
||||
Yeah - It's kinda like taking away the kids toy (by recommendation of the FDA of course) without telling the kid that if he bites it, his head may explode... Or in this case - if you don't uninstall it - you could perhaps have some leacherous web trash hacking in to your hard work, exploiting, not giving a damn about the repercussions.
And it's this point alone which would make at least allowing some sort of transparent information share once a thread has been put in the graveyard. Because just slapping a This modification cannot be downloaded. label on the thread without really giving a care for those who might want to promptly uninstall the tainted modification... IDK... Just seems like an exception to the rule can be made if it goes to benefit the Members of the community. Anyway - without going into detail - I did have to scour the web - finally finding another venue for which to download the modification I had issue with - and me as a licensed member having to go to another vBulletin site in order to download a modification for instructions so that my forum can have no exploits... Well - it seems a bit ridiculous kinda. Perhaps there should be a big bold red note which says Save Your Downloads because You Never Know When It may be Deleted from view. Luckily for my newest forum - I've done just that.... Jacquii. |
#9
|
||||
|
||||
Actually, at this point, the best thing to do is what Jacquii suggested:
Quote:
|
#10
|
|||
|
|||
Having a graveyarded product available is extremely helpful if one has to do a manual uninstall of it. Personally I think that the mod graveyard itself is just a terrible idea to begin with.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|