The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#11
02-23-2009, 04:01 PM
|
||||
|
||||
An easy way to resolve this issue is do the following:
1. Remove author's ability to delete files unless its a security related risk/issue which if I'm not mistaken, usually vb staff removes the file first (?) 2. Force them to leave note upon request to move mod to graveyard, like a fill-out-a-form procedure so to speak and minimum character description (note) required so they can't just type jibberish just to complete the process. 3. Force requests to go into moderator queue for vb staff to validate first (not sure if this is already part of the process) 
|
|
#12
02-23-2009, 04:18 PM
|
|||
|
|||
|
with that much rules, nobody else will take the time to retrieve their hacks from the dB or send them to the graveyard, they will simply abandon them... which is not better because there will be a bunch of abandonned stuff with no support or bugs in the dB.
|
|
#13
02-23-2009, 04:55 PM
|
||||
|
||||
|
We are not going to force members to do anything, nor will we remove an authors ability to delete files. vB.org is not an installation/removal service, we are here to host/provide modifications, it is upto authors to provide instructions as they see fit, and installers to make sure they keep records of any such details.
|
|
#14
02-23-2009, 07:49 PM
|
|||
|
|||
|
we dont need to force users to do anything, but as far as deleting mods/attachments of the zip files, it should be soft deleted not perm deleted, that way if these issues do come up a staff member can simply provide the simple uninstall information. it CAN be done.
really getting tired of alot of ideas we throw @ the vb.org site not being taken up on, and the backlash we get from staff members here like we are shmucks for either deleting a zip file or whatever. like i said before, its not about whats up to a installer to keep records of whatever stuff they do, STUFF does happen like hard drive deaths or formats or accidental removal of data, and we cant get that information back. we are the paying members here. we validate our licenses, pay the yearly fees to jelsoft. vbulletin.org is networked with vbulletin.com license system for the reason to keep legit paying members here and have a orderly system, so there is no reason why things cant be changed to assist the paying customers with slight issues like this.
|
|
#15
02-23-2009, 07:59 PM
|
||||
|
||||
|
In agreement with you Gotti. Any ideas we CUSTOMERS share get shutdown as if we do not matter. There is mostly a 'holier than thou' attitude here.
I've been treated like crap a few times by certain staff members here. My ideas rejected as if I were a fool. I've been corrected unfairly at least once for something that was not my wrongdoing. I reported this a while back to VB com, what do they do? Make lame excuses on behalf of some staff as if VB headquarters has nothing to do with vb org or no control over their own networked site.
|
|
#16
02-23-2009, 08:13 PM
|
|||
|
|||
|
Quote:
btw, i do not share the idea, just stating the known fact!
|
|
#17
02-23-2009, 08:30 PM
|
||||
|
||||
|
Quote:
I don't recall any "fan site" out there that can easily have access to an official site's database like that. Its best you do your research first before just saying whatever you want. http://private.dnsstuff.com/tools/wh...n.org&email=on How ironic? They just happened to be using the same nameservers as well. Quote:
https://who.godaddy.com/WhoIs.aspx?d...rog_id=godaddy Nameserver records returned by the parent servers are: http://www.intodns.com/vbulletin.org ns1.jelsoft.com. ['209.62.16.134'] (NO GLUE) [TTL=86400] ns2.jelsoft.com. ['74.52.166.146'] (NO GLUE) [TTL=86400] ns3.jelsoft.com. ['74.52.82.226'] (NO GLUE) [TTL=86400] http://www.intodns.com/vbulletin.com Nameserver records returned by the parent servers are: ns1.jelsoft.com. ['209.62.16.134'] [TTL=172800] ns2.jelsoft.com. ['74.52.166.146'] [TTL=172800] ns3.jelsoft.com. ['74.52.82.226'] [TTL=172800] Hmm. Not the same company still? Same IP, same server, same nameservers, same registrant and mysterious user database access to vbulletin.com from this site. I guarantee you anything a staff member, probably Paul will either erase this post or lock this thread. You've done that before Paul, shutting us up as if we were loud dogs.
|
|
#18
02-23-2009, 08:42 PM
|
||||
|
||||
|
This site is hosted, and the domain is paid for, by Jelsoft. However, the staff here are not employed by Jelsoft, nor are they in any other way official spokespersons for Jelsoft or its parent company.
There might be some staff on vBulletin.org that are also employed by Jelsoft, but if that is the case then they are paid to answer support tickets on vBulletin, and moderate this place in their space time. Now please, stop being silly and realise that you have to take some responsibility yourself, instead of wanting your hands held all the time.
|
|
#19
02-23-2009, 08:47 PM
|
|||
|
|||
|
this site is the same as the .com. it was made to house the start of the modifications, thats all. if it wasnt for the paying customers, then we wouldnt have to validate our license here to make ourselves seem legit, just so we can download mods on here that people supply for free.
everyone is supposidly a volunteer here, im sure no1 would come out and say "ya i get paid". thats not the point. the point is, we pay jelsoft, we come here for the mods, we validate ourselves as paying members in a system linked together, our request for things should be taken into consideration.
|
|
#20
02-23-2009, 08:52 PM
|
||||
|
||||
|
Quote:
I have nearly 100 mods installed including basic template edits, simple file uploads, once step plugin upload, to more complex mods thereafter. I don't need hand holding nor am I silly for asking a simple thing, to retain original mods when moved to graveyard. What does the author even lose if they do not delete the files upon moving to the graveyard? Seriously, where is the harm on their part?
|
 |
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT. The time now is 11:46 AM.