robojerk wrote:Don't know why I didn't add this earlier. If you use the DragonflyCMS module and want to include the forum name of your applicants on the applications do the following.

Open up apply.php, and look for

Code: Select all

$ffname = Fix_Quotes($_POST['ffname']); 

After it add

Code: Select all

if (is_user()) {
    $userid = $userinfo['user_id'];
    $username = $userinfo['username'];
} 

Then look for the line

Code: Select all

$App = "Name: $GamerName

After it add

Code: Select all

Forum Name: $username

Now your applications will include the account name of your applicants so if accepted you can quickly grant them forum access.

Code: Select all

<iframe src="http://linktotheappgoeshere.com" FRAMEBORDER="0" class="tabnews" width="100%" height="1300"></iframe>

ironforceguild wrote:I'm not trying to sound greedy here, but is this being implemented into the module? If this allows "accept" applications then i can completely switch our website over to the DragonflyCMS system.

Actually, an important question I have... Are you saying that the applicant has to have a forum registered name before they fill out the application? or does filling out the application give them a pending approval forum name? make any sense?

Code: Select all

$ffname = Fix_Quotes($_POST['ffname']); 

Code: Select all

$ffname = ($_POST['ffname']); 

djdevon3 wrote:Try FixQuotes() instead of MagicQuotes()

Code: Select all

//1 Do your form elements
<form name='application' action=".adminlink(Join_Us&amp;file=apply')." method='POST'>
<input type='hidden' name='mode' value='JUSave'>
<input type='submit' value='"._SAVECHANGES."'>

//3 Cleaned variables from case get put into the db
function themecpSave ($xname , $xclass, $xcharacter) {
    global $prefix, $db;
    $db->sql_query("UPDATE ".$prefix."_Join_Us SET name='$xname', class='$xclass', character='$xcharacter'");
    url_redirect(adminlink('Join_Us'));
}


//2 Setup your case switch to mode (create url parses such as Join_Us&mod=)
$mod = isset($_POST['mod']) ? $_POST['mod'] : 'Join_Us';
switch($mod) {

    case "JUSave ":
        // clean the form variables and handle the fixing of quotes here
        $xname = isset($_POST['xname']) ? Fix_Quotes($_POST['xname']) : '';
        $xclass = isset($_POST['xclass']) ? Fix_Quotes($_POST['xclass']) : '';
        $xcharacter = isset($_POST['xcharacter']) ? Fix_Quotes($_POST['xcharacter']) : '';
        JUSave ($xname , $xclass , $xcharacter);
        break; 

Here's how it happens and how most modules are coded.
1. A user clicks on submit and the form is processed using the value JUSave
2. JUSave goes into it's own case where all the variables in the form are defined and cleaned.
3. Output variables are assigned aliases such as xname and are put back into their normal variable but now they are cleaned and php uses that cleaned data to put into the database. I've labeled them numerically in order of process though they are out of order chronologically here because you want the cases to be last for file organizational purposes.