Login required to apply?

By design the module allows only non-anonymous users to apply to postings in order to reduce the potential for mail abuse without needing CAPTCHAs, etc.
Out of curiousity, though, why do you want anonymous users to be able to apply to postings?

I don't want users on my site. And the job postings are for anyone, so anyone can apply. I don't want them to have to login to apply for a job.

I saw that there wasn't a permission setting for "apply for job" but there were settings for everything else like "create, edit etc". Why would I want anonymous users to edit a job posting?

I am confused. Is there a way I can hack it? Can I pass a bogus id/pw for only appliers?

Well.. any help at all would be very.. helpful.

I would like to use this module as an anonymous user. Can anyone suggest how I can make that happen?

Here's your hack at it's simplest. Use at your own risk:

1. remove line 80 in job_posting.module (it's the line that states: 'access callback' => 'user_is_logged_in',)
2. replace line 893 in job_posting.module so that "if ($user->uid != 0) {" instead reads as "if (TRUE) {"

Correction:

1. replace line 80 in job_posting.module so that "'access callback' => 'user_is_logged_in'," instead reads as "'access callback' => TRUE,"
2. replace line 893 in job_posting.module so that "if ($user->uid != 0) {" instead reads as "if (TRUE) {"

i agree that for spamming purposes this would not be advisable but there are situations where would be necessary such as employment/career centers which have job application terminals running a job bank based on this app.

anyhow, would it make more sense to add a checkbox to the settings page (admin/settings/job-posting) or add an extra fieldset to the permissions page (admin/user/permissions)?

and what i mean to say is for me... if i wanted to add this functionality, which way would be most consistent with its current path?

I agree that adding a permission line to access control is the best way to handle this situation.

Same situation for me: we have a site without users/login (just a blog, events, news, etc) and would like to have the option of letting anonymous users submit applications.

Adding one permission line shouldn't be too hard. I'll see if I can manage a patch for those who would like it.

Hi just wondering how this is going? I would also (Foolishly) like to open our job postings to anonymous users. We will not be providing external users with accounts.

With Drupal 6.6 and job_posting-6.x-1.10.tar.gz I have made the suggested edits. I now have the Submit button. Unfortunately the next page replies with Access denied You are not authorized to access this page.

Any assistance would be greatly appreciated. Any other module suggestions? (But I really like this one.)

I also had the same results... the other 1.x dev solution didn't work either...

HEY GUESS WHAT I GOT A WORKING SOLUTION !!!

replace line 80 in job_posting.module so that "'access callback' => 'user_is_logged_in'

with

'access callback' => '1',

and line 893 (ish)

// anonymous user
else {
// displayed link for anonymous user
$variables['joblink'] = l(t('Submit an application'), 'job/application/node/' . $variables['node']->nid);
}

ya thats right ... annoymous postings.. HA!!!

Your 'working solution' is pretty much what was offered in #5 above so I fail to see how it warrants a change to 'fixed'.
Don't forget to implement a CAPTCHA or something to prevent the inevitable deluge...

+1 on this idea! Making someone create an otherwise useless user account just to fill out an application doesn't seem right... even if it means some sort of CAPTCHA.

I've put together a patch!

1. Anonymous users may now apply to job postings.
2. I added a permissions setting... "apply to job posting." Administrators should now be able to define which roles are allowed to apply to postings.
3. I integrated CAPTCHA. If you have the module installed and enabled, the application form will include a maths CAPTCHA. As an added benefit, this also weeds out applicants who can't add or subtract. ;-)

Eventually, I'd like to set up the CAPTCHA integration a little better, so admins can make use of other types of CAPTCHA via the CAPTCHA settings page.

I've attached the patch. It's my first ever, so hopefully I've rolled it correctly!

NB: I converted job_posting.module to Unix (LF) line-endings before generating the patch. It might be necessary to do the same.