Keep applications after accepted

woft

Hello,

Is there a way to keep the applications in the applicants section after they have been accepted or declined, instead changing the accept / decline button to a text saying "Accepted or Declined". Additionally can i keep the Applications menu pop up on the menu even if there is no applicant?

Woft

peregrine

Additionally can i keep the Applications menu pop up on the menu even if there is no applicant?

not sure what you wanted here.

if you want the applicants menu option as an option on your main menu.

add this to your themehooks file....

 public function Base_Render_Before($Sender) {
       $Sender->Menu->AddLink('Users', T('Applicants').' <span rel="/dashboard/user/applicantcount"></span>', 'dashboard/user/applicants', 'Garden.Users.Approve');
    }

and link to a post that you haven't responded to as well

http://vanillaforums.org/discussion/comment/204555/#Comment_204555

I think your applicant approval dashboard screen would become unusable after a while, if you kept a record of every member approved or denied. you would need to just log it as a different type entry if you wanted to.

woft

That is fantastic, I know I ask alot of questions here on the commuuntiy and I am sorry I cannot reimburse you for your time.

In relation to the first part of the application.

When an applicant is on the applicant page, it is removed once it has been accepted or declined. I want a way to keep that application there after they have been accteped or declined, as I have added custom fields that are displayed in relation to their application, such as age, why they want to join, the game they wish to apply for etc etc.

I was thinking, just as i have added custom fields to the applicant view, would it be wise to add them to the user view, so the applicant information is there as well?

peregrine

Aboslutely no problem asking questions. responding whether things worked for you or didn't and following up is better and clicking an insightful or awesome reaction once in a while ain't bad either.

I suppose you could hook into the logmodel and add fields to the log table. then write a custom mod that retrieves info from the logtable. or you could write a custom log that stores all entries during registration process. and somehow hook into that log that stores whether it was approved or denied along with the admin id of who approved it. I haven't researched it, just floating the idea.

or you could look at registration logger plugin and modify it and store your extra registration data info to a text file. - that would be the simplest.

R_J

@woft said:
I was thinking, just as i have added custom fields to the applicant view, would it be wise to add them to the user view, so the applicant information is there as well?

If you have added the fields to the registration process, I expect they are additional columns in the user table. So adding that functionality to the user list would be the "natural" solution since all you want to do is see user information, not applicant information.

You may be able to enhance peregrine plugin Members List Enhanced: http://vanillaforums.org/addon/memberslistenh-plugin
From the description it seems as if you can set it to be viewable only for admins. Adding some fields to it should be easy (I think, @peregrine will know that)

peregrine

@R_J said:You may be able to enhance peregrine plugin Members List Enhanced: http://vanillaforums.org/addon/memberslistenh-plugin From the description it seems as if you can set it to be viewable only for admins. Adding some fields to it should be easy (I think, @peregrine will know that)

Members List Enhanced - one of the more useful add-ons for administrators to get a good handle on their users might as well plug it. maybe someone with funds available will send a donation if they like it.

good idea. it would be another easy way. however, that would only be for applicants that are not denied or other roles because denied applicants become [Deleted_User] but the additional fields he added may not be changed upon deletion. So you would have to allow [Deleted_User] to show when modifying the memberlist-enh, but relatively easy if you pay attention and are careful.

it would be pretty easy to do that if in user table. if in a different table you could always join it the way similar to the way karma table is joined.

peregrine

you might also be able to use the BeforeDeclineUser event and write info to the log in your own plugin.

and write your own entry via LogModel::Insert

woft

Thank you for your help guys,

R_J i took your reccomendation and added it as a <td> in the users page on the dashboard.

I decided not to edit the Members List Enhanced as peregrine states on the plugin page that he would be unable to support the implementation of new features without a monetary contribution.

peregrine

I thought you wanted to store declined user data?

this seems to do it, if you put it in a your own plugin.

 public function  UserController_BeforeDeclineUser_Handler($Sender) {
 $UserModel = new Gdn_Model('User');
  $UserID = $Sender->EventArguments['UserID'];
  $User = $UserModel->GetID($UserID, DATASET_TYPE_ARRAY); 
  $Result = LogModel::Insert("Declined", 'User', $User, GetValue('LogOptions', $Options, array()));

 }

you would need to add Declined to the enum in Operation field in the log table. or do it via structure.

---

@woft said:I decided not to edit the Members List Enhanced as peregrine states on the plugin page that he would be unable to support the implementation of new features without a monetary contribution.

fine by me, whatever works best for you but ...
nothing stops you from modifying the memberlistenhance plugin for your own use. I just don't want to be required or expected to help everyone for every feature they want to make for my plugins.

because it leads to this ....