I'm having a few issues associated with trying to get this module to work. When I install the module, it creates three content types: job, listing-jobappln, and resume. However, none of these content types seem to be configurable in on the permissions pages. There are simply no options for them at all. Under the listings permissions, I've seen the following options:

listing module
administer listings

listing_job module
apply for jobs
cancel any job applications
cancel own job applications
create job
delete any job
delete own job
edit any job
edit own job
manage job applications

listing_jobappln module
View Job Applications

For authenticated users, I've clicked all the options except the "any" options and the "administer" options. By doing this, authenticated users are able to create content of the type "job". However, once they create the content, they are not able to view it. The content page will return the following error:

Access denied
You are not authorized to access this page.

For administrators, the problem is slightly different. They do not receive an error message, but they are also not able to see the job content. Instead, they see the title, and below that, they see what appears to be an embedded view showing the number of applications:

Job Applicant Resume Date Operations
No job applications.

Any idea what is going on here?

CommentFileSizeAuthor
#15 listing_jobappln.zip4.03 KBNewZeal
#13 listing_jobappln.zip4.06 KBNewZeal
#11 Untitled-2.jpg141.83 KBNathanM

Comments

NewZeal’s picture

NewZeal commented

OK first, the listing_job module was affected by CVS problems I had which resulted from the fact that I copied this from the jobplus module which is going to be deprecated once this one is working correctly. In order to avoid name conflicts I had to rename the functions. The alpha7 version ended up calling the job application content type listing_jobappln when it should be job_appln for legacy reasons. So this is corrected in the current dev release. I'm spending this week sorting out issues and will do another release later in the week.

The other problem with content types is that I am still undecided on how to create the content types, whether to use the module hook system or use CCK. Since D7 includes an integrated CCK I normally choose that as the preferred option and import it using content_copy however at the moment the listing_job module uses the hook system and listing_jobappln uses CCK. When CCK is used, then permissions are all within the node area and not within the module area.

I do have the listing_job modules running on a site and am not experiencing the problems that you describe regarding access denied. Try disabling the module and reinstall.

If you have the job application module installed you will get an embedded view of applications displayed to users with the right permissions.

NathanM’s picture

NathanM commented

I have disabled the modules and reinstalled. By doing this, I've managed to get rid of the "access denied" page, but it still doesn't appear to be working properly.

Relating to the embedded view, I feel like that could be part of the problem. The embedded view completely replaces the node content, so even if I have the right permissions, I still can't see the information for the job that I've submitted.

Regarding permissions, my problem is that the permissions aren't being created in either the listing module, the listing-job module, or the node module. There are simply no relevant permissions that I can set for the content type "job", and "listing-jobappln". There also doesn't seem to be any way for me to delete the content types and create new ones. When I disable the listing modules, these content types disappear from the administration pages altogether, (for some reason, "resume" is still available and has a set of permissions).

Also, when I tried to re-enable the modules I enabled the listing-menu module for the first time and was initially greeted with the following error:
"Fatal error: Cannot redeclare menu_overview_page() in F:\UniServer5_6b\UniServer\www\hkscene.com\modules\menu\menu.admin.inc on line 12"

Refreshing the page once seemed to get rid of this error, but I then saw this when it returned to the module page:

* The content type jobappln already exists in this database.
* Exiting. No import performed.
* The content access permissions need to be rebuilt. Please visit this page.

* job application content type created
* resume content type created
* The configuration options have been saved.

I proceeded to rebuild the content access permissions. After this, I didn't receive the "access denied" error, but I also couldn't view the node content, either. No matter who the author of a node is, I don't see any node content, just the view listing job applications. This goes both for administrators as well as authenticated users. In fact, authenticated users are seeing the application view even though the "administer listings, manage job applications, and View Job Applications" permissions are all unchecked for authenticated users. The only options that are selected for authenticated users are as follows:

apply for jobs
cancel own job applications
create job
delete own job
edit own job

So why are they still seeing this view instead of node content, and how is anyone supposed to be able to apply for jobs with this?

NathanM’s picture

NathanM commented

I should add that I've flushed the cache on this several times throughout this process, as well, so I don't think that is the problem.

NewZeal’s picture

NewZeal commented

You might have to let me have a quick look at the install. Contact me via my form.

NathanM’s picture

NathanM commented

I'm only on a localhost right now. I will try to upload a test server later this week, and will contact you then.

NewZeal’s picture

NewZeal commented

I've double checked my code and the view does not replace the content. Check your setup to make sure that you don't have a module or some setting which is obscuring the body content. At present this view is simply added to the body content, so the field is definitely displaying if that view is.

NathanM’s picture

NathanM commented

Hello, I sent you an email via the contact forms. Please let me know if you find anything.

Best Regards,
NathanM.

NathanM’s picture

NathanM commented

Ok, using the updated listing_job.module file you sent me, I am now able to view the node content and click the link which says "apply for jobs". However, when you click on that link, it is not currently taking you to a listing_jobappln content creation from, but rather displays the message "Thank you. Your application has been submitted." When I check my content listing page, it shows a new node was created, but it is of a blank type, and contains a copy of the job listing. The author is also listed as the job creator, rather than the person who is applying.

NathanM’s picture

NathanM commented

Also, I could be wrong, but is the application supposed to be sent to the job creator? If so, it is just sending blank emails at the moment.

NewZeal’s picture

NewZeal commented

What happens when you apply is that, if you have one resume then you will just get the message 'applied for this job'. If you have more than one you should get options to select one. I have thought that we could do with a 'are you sure you want to apply form?' before the application is made.

When an application is made the application is auto-created and the applicant does not see it. I originally had the idea of presenting the applicant with a field for making a brief statement regarding their application before they apply, but that is not in place. After you apply for a job with an applicant, check using the job owner if any applications have been made for that job. Most of the functionality for a job application is for the job owner to view, sort, make comments, assign them as good, bad, ugly etc. The job application currently consists of the applicant's resume embedded in the body field.

NathanM’s picture

NathanM commented
StatusFileSize
new Untitled-2.jpg141.83 KB

The problem is that if there is no resume, it isn't attaching anything. It also isn't creating the job application as listing_jobappln content type. It is just a blank content type which clones the job node, not any resume node.

I personally would be very much in favor of a "Are you sure you want to use this resume" screen, or a "Choose from your following resumes or create a new one" type of screen. That is one of my main issues with job search, is that it just assumes you want to use one resume if you only have one.

NewZeal’s picture

NewZeal commented

ok. I'll have a look at it tomorrow.

NewZeal’s picture

NewZeal commented
StatusFileSize
new listing_jobappln.zip4.06 KB

I've found the bug and fixed it. Resumes were not processing correctly. The fixed module is attached and committed to dev. You will have to clear your cache after you upload it.

NathanM’s picture

NathanM commented

Ok, now the issue is that it won't create the job applications because it doesn't recognize that I have resumes created. When I try to apply, it tells me that I need to create a resume. It doesn't seem to recognize the resume content type, as the create node link reads like this: /node/add/0. This takes me to the main content creation page, where I have to manually select the resume content type. Once I create the resume and click on the apply link again, I am once again informed that I need to create a resume.

Once this issue is sorted out, it may also be a good idea to include a redirect from the resume creation form back to the job node. Just an idea.

NewZeal’s picture

NewZeal commented
StatusFileSize
new listing_jobappln.zip4.03 KB

Ok, bug fixed. I apologise for this. Hopefully that is the last bug stemming from the module transfer. I have included the redirect so that when you create the resume you go back to the job node. Another improvement I should make is to add a confirm form because applying for a job is a one time only chance and people need to be prevented from doing it prematurely.

Module attached and committed.

NewZeal’s picture

NewZeal commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.