The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
Reporting A Coder ..
Is there any way on here of reporting a coder for poor work that they completed?
I know on my site you can make comments about poor work completed at a dealership .... I think that people should know what happened Cheers |
#2
|
||||
|
||||
There is no mechanism for this at the moment. However, some sort of feedback system is part of the current projects being discussed. ATM, our priority is moving to vb 3.6, after that, the other projects will start to be looked at.
|
#3
|
||||
|
||||
A good idea as I feel that even though paid work is not vb.org's responsibility .. It would be good to let others know when something has gone wrong so others do not have to go through it!
|
#4
|
|||
|
|||
What about when things go right? There should be a place to praise a member's work.
|
#5
|
||||
|
||||
Any feedback system would allow positive or negative comments.
|
#6
|
||||
|
||||
Absolutly it works both ways and gives us an idea of who to use and who not to use ....
After what has happened to me I know who I wouldnt use again. |
#7
|
|||
|
|||
Some kind of testimonials section makes sense for a place like this.
|
#8
|
|||
|
|||
Quote:
|
#9
|
||||
|
||||
Do you know something we don't then ? or is that just another childish comment.
|
#10
|
|||
|
|||
I'd agree Psionic is portraying himself very childishly but you have to admit he has a point. For a site that's packed with vB coders, coding stuff happens incredibly slowly.
|
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|