Clone the job posting module or recreate its features?
Hello,
I am contacting you on behalf of a graduate Web 2.0 English class tasked with creating an internship site for our graduate program. We've hit a snag and would be really appreciative if anyone here might be able to weigh in on the issue.
Originally, we planned to simply list the internship provider's contact information and leave the internship seeker to apply for the position via their own email client outside of the site. A few weeks ago, however, one of our students uncovered the Job Posting module found here : http://drupal.org/project/job_posting .
We instantly took a liking to it because it enabled internship seeker to respond directly to a posted position. The module places a "submit an application" link at the bottom of each position and allows users to submit an application (complete with cover letter and resume) directly to the person who posted the internship.
Yet, as is, it's not exactly what we need. Specifically, we would like to be able to change the "job" terminology to "internship" and add additional fields to the form. After consulting the job posting issues page, we discovered the module developer has no plans to integrate additional features (due to time constraints) and did not find a solution to either of these concerns in past user-submitted issues and support requests.
Our ultimate questions are thus:
1. Is there a way to clone the job posting module and then modify it ourselves?
or
2. Might someone suggest what other modules we might combine to reach the same functionality of allowing users to submit internship applications to businesses directly through the site?
We thank you for your help in advance and look forward to reading what suggestions you might propose.
Jenni
Supply patches
The normal way to approach this is to either discuss this with the current maintainer and implement these extra features your self or just create the features you want. After you've done that it is really appreciated if you give back the modifications to the community; i.e. post the patches in the issues queue for this project. That way the maintainer can integrate features that are relevant to a large group of users into the job_posting module after which everyone can benefit from your work which would make the Drupal project as a whole stronger which in turn benefits you :)
Another way to approach your problem is with CCK and Views. You could create two content types, one for available internship positions and one for internship applications. A similar system is described in one of the first chapters of the 'Using Drupal' book.
Good luck with your project!
thanks for your response
Hi--Thanks for taking the time to share some options with us.
We'll contact the maintainer to talk to him about it just to cover our bases. I'm afraid, however, that we are English grad students with only moderate technical abilities. I might be mistaken (and any of my classmates following this thread can correct me if I'm wrong) but I don't believe any of us have the technical skills or know-how to create patches/new features.
We'd planned on using CCK if we can't modify the Job Posting module. Is there a way to create a content type that will automatically be emailed to another user upon its creation? In other words, could we set up a system where a internship seeker would create new "internship application" content that would then be sent on to an employer upon submission?
Thanks once more!
We can help
Hi,
this can be achieved by using the rules or workflow-ng module.
you need to creat an event when a new content has been created add the action send an email for the required roles.
I hope this help. Need more help you can drop a line.
Regards
Sagar
DIY approach
I, too, am using this module for another purpose. In my case, I needed a file Downloads page, where registered users could upload/download files to be shared on a project.
I hacked the job-posting.module file and changed the words "job posting" that appear on the form page to my desired term. Unless you are quite PHP savvy, I would not recommend doing a full search-replace -- you don't want to change any variable names, only display text. So, go line by line.
EXAMPLE (where I have made some mods):
// declare our node types
return array(
'job_posting' => array(
'name' => t('Download Posting'),
'module' => 'job_posting',
'description' => t('Create a download posting.'),
'has_title' => TRUE,
'title_label' => t('Title'),
'has_body' => TRUE,
'body_label' => t('Description'),
'locked' => TRUE,
),
);
}
But, it would be great for someone skilled to duplicate this lovely module for the other purposes. Would be very easy for an experienced module developer.
_
Not likely-- these types of vertical single use case modules are pretty much obsolete with the d6 advances in cck and views2 and soon to be panels3. It's just not worth the effort to maintain that type of module any longer.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.