Hey guys Im thinking of bulding a recruitment block and not sure if it should be a roster addon or a DF module/block. I would like it to have a form that will allow admins to put in the amount of toons needed for each class and also query roster for how many of each class there already is.

You can see the block in action at
http://wow-deception.com/index.php
Here is the block code so far.

Code: Select all

<?php
//var for how many we need
$druid_n = '1';
$hunter_n = '1';
$mage_n = '1';
$paladin_n = '1';
$priest_n = '1';
$rogue_n = '1';
$shaman_n = '1';
$warlock_n = '1';
$warrior_n = '1';
//var for how many we have
$druid_h = '1';
$hunter_h = '1';
$mage_h = '1';
$paladin_h = '1';
$priest_h = '1';
$rogue_h = '1';
$shaman_h = '1';
$warlock_h = '1';
$warrior_h = '1';
//Forum link for recruitment
$forumlink = '/ForumsPro/viewforum/f=3.html';
//Links name
$forumlinkname = 'Apply Here!';
//Table border
$border = '0';
$w = '20px';
$h = '20px';
//block content
$content .= '<center><table  width="100%" border="'.$border.'">
<tr><td class="row2" colspan="2"><center>Class</center></td><td class="row2" >H</td><td class="row2" >N</td></tr>
<td class="row1"><img src="/images/wowrosterdf/Interface/Icons/Ability_Druid_Maul.jpg" width="'.$w.'" height="'.$h.'" /></td>
  <td class="row1">Druid</td>
  <td class="row1">'.$druid_h.'</td>
  <td class="row1">'.$druid_n.'</td>
</tr>
<tr>
<td class="row2"><img src="/images/wowrosterdf/Interface/Icons/INV_Weapon_Bow_08.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row2">Hunter</td>
 <td class="row2">'.$hunter_h.'</td>
  <td class="row2">'.$hunter_n.'</td>
</tr>
<tr>
<td class="row1"><img src="/images/wowrosterdf/Interface/Icons/INV_Staff_13.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row1">Mage</td>
  <td class="row1">'.$mage_h.'</td>
  <td class="row1">'.$mage_n.'</td>
</tr>
<tr>
<td class="row2"><img src="/images/wowrosterdf/Interface/Icons/Spell_Fire_FlameTounge.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row2">Paladin</td>
  <td class="row2">'.$paladin_h.'</td>
  <td class="row2">'.$paladin_n.'</td>
</tr>
<tr>
<td class="row1"><img src="/images/wowrosterdf/Interface/Icons/Spell_Holy_LayOnHands.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row1">Priest</td>
  <td class="row1">'.$priest_h.'</td>
  <td class="row1">'.$priest_n.'</td>
</tr>
<tr>
  <td class="row2"><img src="/images/wowrosterdf/Interface/Icons/INV_ThrowingKnife_04.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row2">Rogue</td>
  <td class="row2">'.$rogue_h.'</td>
  <td class="row2">'.$rogue_n.'</td>
</tr>
<tr>
  <td class="row1"><img src="/images/wowrosterdf/Interface/Icons/Spell_Nature_BloodLust.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row1">Shaman</td>
  <td class="row1">'.$shaman_h.'</td>
  <td class="row1">'.$shaman_n.'</td>
</tr>
<tr>
<td class="row2"><img src="/images/wowrosterdf/Interface/Icons/Spell_Shadow_Cripple.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row2">Warlock</td>
  <td class="row2">'.$warlock_h.'</td>
  <td class="row2">'.$warlock_n.'</td>
</tr>
<tr>
<td class="row1"><img src="/images/wowrosterdf/Interface/Icons/INV_Sword_25.jpg" width="'.$w.'" height="'.$h.'"  /></td>
  <td class="row1">Warrior</td>
  <td class="row1">'.$warrior_h.'</td>
  <td class="row1">'.$warrior_n.'</td>
</tr>
<tr>
<td class="row2" colspan="4"><center><a href="'.$forumlink.'">'.$forumlinkname.'</a></center></td>
</tr>
</table></center>';


Looks nice, personally I prefer it's better as a DF block with roster dependency..., but would be nice it used something similar to Black templars join_us form and post it in forum directly

Yeah im working with the join_us mod as well and would like this block and the join us mod to work together.

I agree with all of the above.

Having a recruit block that worked with the join_us block would be great. It would be even more awesome of they could write to the forums directly.

I think I would prefer that they be DF blocks with Roster dependency. I try to keep my Roster restricted to register members of the site only; which is only guildies. I would like a DF block that would be viewable by anyone that comes to visit the site; same with Join_Us. Once people see that we have an opening with the recruiting block, apply with the Join_Us module.. and get accepted.. then they have full forum access and access to the Roster.

=)

apply with the Join_Us module.. and get accepted..

I love this idea but how do we tie the Join_Us into a Registration module for DF where a class leader (moderator or admin) could click on an a aprove button. Or should the site be tied down to groups and let anyone register but they can not see anything you do not want a regular registered user to see then have the join_us module post to a class forum where class leaders(group moderator) can look over and then goto the Join_Us Module to approve them. How much data from Join_Us should be stored into the DB, how much of it should be auto fill based off of login is_user() if done by groups?

Looks real nice mate, i would have to agree with the above and think it would be best a df module. I like to keep the roster viewable to only our members not registered or visitors

Right now, I have my forums as invisible, and jst grant them access to members (gtroup, not registered), so for me, I think best would be that join_us register member with the username he/she gived (maybe same password), at the same time, it posts on an officers only forum ,a new thread with the data he entered on the join_us... officers review, and update it's forum access to member in case he/she makes it...

Don't think an aprove button is needed, is not htat hard to put somone on a group

I did something similar for php-nuke. It includes a module for setting whether recruitment is open or closed and the current desireability level for each class. It ties into a Recruitment module that is configurable (ie guild name, message, etc...) and this page includes a link to an application form.

You can see it all here : http://www.black-blades.org (block is on the right side of the main page).

I'm certainly not a php guru by any means but I'd be happy to share with anyone that would like a copy (just shoot me a PM).

Ymryl wrote:I did something similar for php-nuke. It includes a module for setting whether recruitment is open or closed and the current desireability level for each class. It ties into a Recruitment module that is configurable (ie guild name, message, etc...) and this page includes a link to an application form.

You can see it all here : http://www.black-blades.org (block is on the right side of the main page).

I'm certainly not a php guru by any means but I'd be happy to share with anyone that would like a copy.

I'd be interested in the block and Recruitment module.

Anaxant,

Looking forward to the release of this block!

RottGutt

Cablespider, check your PM's, I have sent you a link to download it.

I think there there is obviously a lot of possibilities as far as module/roster/DF intergration, all with varying levels of complexity for both the developers and also for the end users (applicants, officers, GMs, site admins).

For myself and how I would like to run things, this sounds the best and the simplest (but I have no clue about developing):

* Items of Note:
- I have a public section of my forums where any visitor can view/post
- 90% of forums are only displayed to registered users
- I do not approve DF apps unless the username they are registering matches exactly to a WoW toon name of a guildie. I regularly compare my DF memberlist to my Roster list, and drop DF users who are no longer in the guild.

1. Join-Us would post to a forum called "Pending Applications" instead of getting email off, or both. (the module would be usable by all site visitors)

2. Officers/Mods would review the posted app, and decide to accept or deny the user.

3. Manually, an Officer/Mod would just move that post to either the "Accepted Apps" or "Rejected Apps" thread, for future reference.

4. Person gets their WoW toon accepted to the guild. We tell them to register at the website (if they did it previously, their req. was denied, since they weren't in the guild) and it gets accepted this time around.


Doing things this way is a teensy bit of work, and requires that I keep Roster updated regularly; we actually try to do it daily. and admins have to stay on top of pending site registrations.


Obviously, it would be awesome if there were a way to tie Roster, DF registration, and a solid recruiting process all together, but between:

1. submitting guild app
2. officers accepting or denying via a website
3. sending guild invite in game
4. updating Roster
4. user registering for DF
6. pending registrations compared to Roster
7. DF registration accepted or denied

It seems like integrating them all would be a big pain in the ass. =D I am all for ideas though, as I am well aware that many of you are way smarter than I. =)


As a site admin and guild officer, here is the thing that I think make all processes easier:

DF user name is identical to the users WoW main character name, who is in the guild. This is a requirement for me. I don't want "Allistar" in the game-guild to be "Bob" on my website. Wayy to complicated.

This makes the application process harder on a website, if you are talking about tying applications to DF registrations.

Say person Bob plays character Allistar. He applies to guild as Bob using Join_Us.

We like bob's app. We decide to accept him. If registration is integrated, and we now accept Bob, he gets a "Bob" DF username.

In game, we now invite him.. so we end up inviting Allistar.

Now the game and Roster will not match DF, and I have to keep track of who is who, or go edit accounts, or have him re-register, etc. Lame.


I don't see that there is any easy way to integrate guild acceptance and site registration completely without it becoming a huge clusterhump over time.

Thats my two cents. Please please prove me wrong!

Do all of you have registration open to everyone on your sites? Doesn't this cause mass confusion?

I locked down registration on my site (going so far as to remove any links to it). All accounts are created by hand by either myself or one other individual (I have only allowed three people admin access). Logins are always the main characters name, this avoids confusion on the forum, you actually know who it is that has posted.

I have separate groups setup with access to various areas of the forum tied to group membership (i.e. Officers have full access to everything while Veterans can't see the Officers forum areas, Members can't see the Officer areas or the Veteran areas, etc...).

When an application is submitted, an email is sent and this automatically gets forwarded to several Officer emails (those individuals tasked with posting the apps in the forum). The application is then reviewed by all of the officers and voted upon.

If an application is approved, the applicant is invited into the guild, a website account is created for them and they are added to the recruit group. The forum posting containing their application is then moved into another area for discussion during their recruit phase (generally 30 days or so).

If an application is outright rejected, either due to being incomplete or for some other reason, it is moved into a rejected application forum area. Placing it there allows you to do a quick search for the character name when a new application is posted (you'd be supprised how many people will try to apply several times over a year or two).

Following the recruitment phase, the person is either elevated to member rank or removed from the guild. The forum posting is then moved into either an "Approved" area or a "Rejected" area, again allowing us to do a search later if needed.

The phpbb area of this forum has some promising development going on in terms of linking the WoWRoster member rank tables to the forum group tables. I'm really hopeful that we'll be able to get this tied into phpnuke (or Dragonfly) as this would make the maintenance of the website accounts a lot easier. Currently I sit down every couple of weeks to do account maintenance (EQDKP is another separate entity that has to be dealt with as well). The addition of the member log to WoWRoster has made the de-activation of accounts for departed members a piece of cake, the tying together of the rank and group will remove a lot more time for me.

Now, if someone was to come up with the code to automagically post an application into the forum (eliminating the emailing process), that would also be awesome!

Yeah. If you want a nutshell version of what I posted earlier; read the post above this one. hehe

Seriously though, I had forgotten about having a way to handle trial memberships (30 days to evaluate a player or whatever).

Currently, my guild is super-recruiting, as we are very new and small, but this will become an issue soon. In which case, I would probably handle it as you have stated above. We already have forum groups and special permissions and all of that set up.

This could be cumbersome but could be ideal in the end. Say we make recruit forums for each class with an accept and deny subforum. I still think group permissions would be best as in time we could auto create groups and add to them via addon triggers. This way we could have the guild app post to class based forums where we would expect the class leader or officer to make the choice then once added to the guild in game he would be added to the correct group then the officer would either add that app to the accept or deny list.