That email address field doesn’t always exist/isn’t always set, so relying on it for the application method isn’t a good idea.
Regarding alerts though, I have this snippet for expired jobs: https://gist.github.com/mikejolley/88ff07584c36e22055aa
It could be adapted for approved jobs by using the filer ‘pending_to_publish’ instead of ‘publish_to_expired’.
Thread Starter
eckul
(@eckul)
Thanks I am planning to make the email address field required so I can use it for this purpose. Do you know of anyway to send all applications to it? Also in regard to the alerts I wasn’t able to get it working, do you know what other areas of the code i would need to change? or can you point me in the right direction? Thanks again.
I’ve toyed around with this suggestion, and experimented with two methods:
1) Filtering the application method and swapping out the email
2) Hooking into the job submission form and updating the value based on email
Neither works perfect though, and can break based on other settings. You also lose the flexibility of allow users to customise this per job.
What if, instead of this, we set the placeholder of the application method to the logged-in users email address. That would save manual input and its something I would be willing to code into core.
On top of that, we could add an option to limit that field to just emails, rather than URLs, which would also be good if you wanted to ensure an email address was used.
From your side you would force registration. Add added benefit to this would be that job posters would have an account associated with each job post. Then you could use http://wordpress.org/plugins/post-status-notifier-lite/ for your approval alerts too.
Does that sound good?
Thread Starter
eckul
(@eckul)
Hi Mike, thanks I think that would work as long as the process from registration to job posting is reasonably seemless. Thanks for your response, it’s very much appreciated. Let me know how it goes. Cheers
