Here?s a Scenario:
You have a board with 1000 members. You decide you want to add a new required field to your members profiles. Well everyone who registers after you add the new required field will be required to fill it in to complete registration (makes perfect sense ). But your 1000 existing members can skate by without updating and continue to go about posting and such.
This hack forces your existing members to update the new fields you?ve added to the profiles. You can set it so that once members log in and try to view the board, reply to a post, post new topics, search forums, and so on, they will instead get a message that tells them they need to first update the new fields in their profile before they can go any further.
Why use this hack?
Even if you tell your members to go and update the new profile fields they won?t always do it. But if they are forced to do it before they can post or view the board then they will do it.
What am I using it for?
I have 300 existing members and I now want all my members to be searchable by their location and key interests. But my members need to have this information in their profiles before anyone can get any results. So I'm forcing them to put this new information in. Doesn't sound nice but it's needed to make the system work. This hack gives me the power to force members to update that profile before they can do anything they want to do on the board.
What can you restrict?
ForumDisplay, Calendar, Newreply, Newthread, Poll, etc.
Warning: Do not use this hack on usercp.php. Your members need access to edit their profiles.
Step by Step;
Step 1. Open up the file you want to restrict (i.e. newreply.php)
Step 2. Find:
PHP Code:
require('./global.php');
Under it put:
PHP Code:
// +++++++ Start Erroring Missing User Profile Fields [ Start ] +++++++
function chkprofilefields($userid, $n) {
global $DB_site;
$fieldnumber="field$n";
$getu=$DB_site->query_first("SELECT $fieldnumber FROM userfield WHERE userid='$userid'");
$field=$getu[$fieldnumber];
if(empty($field)) {
eval("standarderror(\"".gettemplate("error_emptyrequiredfields")."\");");
exit;
}
}
// +++++++ Start Erroring Missing User Profile Fields [ End ] +++++++
Step 3. Log into your Admin CP and go to "User Profile Fields > Modify".
Hover your mouse over the edit link of the forum you want to make your exisiting members require to fill out. Note the last number in the url ( the profilefieldid= number). Write it down.
Step 4. Replace the ## in the code below with the number you just wrote down.
PHP Code:
chkprofilefields($bbuserinfo[userid],##);
Now put that last code right under the larger code given above. Note: If there is more then one profile field you now require then add another line of that last code underneath the previous.
Example;
Repeat this process for whatever files you want to suspend from your users until they fill in the new profile fields (i.e. forumdisplay.php, newthread.php, calendar.php)
Step 5. Create a new template called: error_emptyrequiredfields
Place the folowing message in it (or whatever message you would like):
Quote:
Before you can go any further you need to update all profile fields that are now required on the forum. You can view your UserCP>Edit Profile and update it there. Thanks in advance!
Step 6. Smile That's it!
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
I added roxics code to my 2.2.0 and it seemed to work like a charm until some users began complaining about not being able to post due to "field is required" message.
Field was already filled in, so why the message appears?
Would firefly's solve the probem? I can't see a relation between the field contents and the quey not being able to retrieve them.
Couldn't you just put this function in the functions.php and use the "chkprofilefields($bbuserinfo[userid],##);" line in the files you need to instead of having to have the whole function code in each file?
Force Profile Update Hack Details »»
It is being release with his permission. 
About Developer
Visit Web Site
No support by the author.
02-19-2003, 11:41 AM
