No, the way my users want to use it goes like this:
Member A wants to post something up but doesn't want everyone to see it. Member A puts a password on her thread. Members who want to read it send a PM to Member A asking for the password, and Member A can either provide it to them or decline, depending on her feelings at the time.
This comes in useful for stalking situations, or fighting amongst members, or cases of sensitive information.
Or say you have a medical board, and a member wanted to post some specific medical info, and have it available for certain members or mods to see, so she would post the medical info, put a password on the thread, and give the password to those who she wants to see it.
in contrast, if she did it in a private group, you might have a private group with 100 members in it, but that still does not mean you want all 100 members of that group to see a sensitive item -
Again, it can be done by PM, but if it's a thread on a baord that stays, then it can easily be referred to by the member and other people as time passes, rather than searching for a PM, or having the PM have already been deleted from people's inboxes.
It just gives a much more pin-point like control for the member over who exactly gets to read a sensitive thread.
Not something that most boards would use every day, but it would be useful in certain situations.
Simple. Make a bbcode to wrap around what you don't want seen. Then do a preg_replace with a conditional in the postbit_display_complete hook. You could do a profile field for the password needed. It would entail a bit more than that but that is the basic procedure.
05-17-2008, 08:55 AM
Threaded Mode