What I really want to know is:
How is it possible to show to the end-user - which is for whom we are even discussing this in the first place - that a hack has been Verified/Approved/Optimised/$vbphrase[whatever_the_bluest_of_fks_youd_call_it], without adding a label of some sorts?
Coming to you guys for help isn't enough? You want to make them feel smaller still?
What I really want to know is:
How is it possible to show to the end-user - which is for whom we are even discussing this in the first place - that a hack has been Verified/Approved/Optimised/$vbphrase[whatever_the_bluest_of_fks_youd_call_it], without adding a label of some sorts?
You can't... But you can still filter them out. Which is unnoticable.
Quote:
By, us, I didn't necessarily mean me.
Of course you did. Come on, Mod, take responsibility for your words.
One things that does come to mind about such a system is PHPBB's mod-approval system. I remember reading a post in which someone from their "QA" team said "Due to the amount of mods in the queue waiting to be processed, it may take a month or more before they are released" (or words to that effect)
If such a system where put in place here, then the same problem could occur.
One things that does come to mind about such a system is PHPBB's mod-approval system. I remember reading a post in which someone from their "QA" team said "Due to the amount of mods in the queue waiting to be processed, it may take a month or more before they are released" (or words to that effect)
If such a system where put in place here, then the same problem could occur.
In the first post of this thread, where does it say anything about approval?
Even though I am not Kirby, no it was not updated. I don't think anything has changed...
globalize became $vbulletin->input->clean_[array_]gpc() and $DB_site became $db, but those changes are pretty minor - just the examples need an update.