If the user has one resume on hand, I think it would be a great option to automatically apply for the desired job with that single resume. For example, if you are using the nodeprofile module to limit the user to one resume, what's the point of asking them what resume to apply for the job with. It should be assumed that they want to apply with the one resume they're limited to. Of course, if they have more then one, then it should ask them which resume to use.
To add this feature, in the job_apply function in job.module, add the following commented code:
if (!$resume_list) {
$msg = t('Please !create to apply', array('!create' => l(t('create a resume'), 'node/add')));
drupal_set_message($msg);
drupal_goto("node/$job_nid");
}
// -------------------
// NEW CODE TO FORWARD THEM IF THEY ONLY HAVE 1 RESUME
if(count($resume_list) == 1) {
drupal_goto("job/apply/$job_nid/$resume_nid{$resume_list[0]['nid']}");
}
// END NEW CODE
// --------------------
$output .= '<br/>' . t('Position: ') . $job->title . '<br>';
$output .= '<br/>' . t('Select from your resumes below, or !create',
array('!create' => l(t('create a new resume'), "node/add")));
$output .= '<br/>';
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | job.module.patch | 667 bytes | robloach |
Comments
Comment #1
kbahey commentedNeed a proper patch for this please. See http://drupal.org/patch
Comment #2
robloachSure thing... See attached.
Comment #3
kbahey commentedCommitted to HEAD and 5.x
Thanks
Comment #4
(not verified) commentedComment #5
b.hughes commentedI have some serious reservations with this patch. For one thing it's too simple, as the OP stated it should be an option, not by design to operate this way. Even if the applicant has only one resume on hand, they might want to modify or review it before sending. As this patch is written, an applicant might get a nasty surprise that when they clicked on "Apply for this job" and their resume was sent without any review.
While it does add another step, I liked it the way it was. I can see the point of the OP though.
To satisfy the OP, I suggest a permissions based method. In the access control section, either under "resume_access module" or another new "resume_module" section there should be an option to allow multiple resumes. If the role is not allowed to create multiple resumes and there is one already on hand, then it goes straight away. It would be up to the site admin to inform people of this feature and that the resume on-hand will be sent without review.
I'd like to leave this open for discussion rather than submit a patch. A patch could be created later if people decide what option they would like.
Comment #6
kbahey commented@b.hughes
A permission for this is overkill.
An option sounds like a good idea. The site admin decides how their site operates.
Go ahead and submit a patch for an option in the settings.
Comment #7
cordis commentedIt's great to find this!
I have reverce this patch!
No more misclicked job aplications!
Comment #8
NathanM commentedIs there a chance to work this in as an option for the 6.x branch? Right now, if you have only one resume, it automatically applies for the job using that resume. If there are none, it prompts you to create one, if there are two or more, it also gives you the option to choose your resume and/or create a new one. Would be nice if this was also the case with one resume.
Comment #9
xamountI have created this special permissions. It is now in the 6 and 7 branches.
Look for a new permission "Force jobseekers to auto apply for a job if at least 1 resume exists"