The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
![]()
No one is taking it as an attack, you are making one small mis-understanding in to a big problem over nothing.
Zachery has explained himself and that's really all that can be done. If we leave these kind of threads open in the public forums it leads to people taking sides. These type of things are best done in private by contacting one of the admins and letting them handle the issue, if you want to go above an admin Wayne Luke is the guy you should talk to. As for why your first thread was closed, there was already a large thread in site feedback related to the upgrade here: https://vborg.vbsupport.ru/showthread.php?t=97215 There is no ETA on the upgrade, when it happens it happens. |
#12
|
||||
|
||||
![]()
Threads merged and re-opened.
|
#13
|
||||
|
||||
![]()
I think there has been some misunderstandings here. The reason he stated that these threads are slowing the progress is that for each one that is created, those that are working on the upgrade are having to stop what they are doing to answer them. That is impairing the overall flow. The fact of the matter is that vbulletin.org is currently fuctional and providing services as expected per the theme.
As far as attitude goes, you have to remember that a lot of the staff here were chosen based on their background in coding. I am not trying to be mean, but coders in general are not the most customer service oriented people. Also keep in mind the general age demographic of vbulletin. This reflects largely on the corporate culture of vbulletin. They are able to provide such revolutionary products because of this culture. Although regulated by Jelsoft, vbulletin.org is staffed by volunteers and are not paid. This means that certain personal responsibilities take precedence of certain obligations of vbulletin.org. This is why they must have a larger staff then what may be expected of a site of this size. |
#14
|
||||
|
||||
![]()
Oh, thought it's 3.5 already here
![]() |
#15
|
||||
|
||||
![]()
Everyone must also remember that although we are part of the staff here, we are also members and we have opinions and ideas just like everyone else. That doesn't mean when we are contributing in a debate thread, that we are representing Jefsoft or the staff here while posting in that thread. I enjoy as good debate as well as the next member. True, being staff does bring with it a certain amount of responsibility. But I for one will never use (and have never used) that position while posting in a thread that I am contributing to.
![]() |
#16
|
||||
|
||||
![]() Quote:
Besides where else could you call boofo booby and get away with it. ![]() |
#17
|
|||
|
|||
![]() Quote:
Do you run a decent sized BBS? If you did/do, and were inundated with questions of that nature (especially since the topic at hand has been covered in the past), eventually some sort of verbal rhetoric would come out of you too, wouldn't it? Seems pretty mild for a response, I think you're exhibiting a little too thin of skin personally. |
#18
|
||||
|
||||
![]() Quote:
|
#19
|
||||
|
||||
![]() Quote:
Most are more concerned with the implementation of the hack database. |
#20
|
||||
|
||||
![]()
This is probably a dumb question, but how would you rather see duplicate threads be handled? Should it have been merged with existing threads on the matter?
VB.org gets a LOT of duplicate threads, and I'm not sure why. Wouldn't it drive you batty on your own site to have a lot of threads asking the same question and then have to give the same answer over an over again? Is it not better to point to the existing conversation and close the duplicate or to merge the duplicate? |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|