Having a few more issues now that I've got views integration.
1. On the employer applications view, there are four columns to the table:
Application
Job
Job Applicant
Applications
The last one appears to be linked to a view of all the applications for that particular job. However, clicking on it takes you to a "page not found" screen. The link structure is /applications/[jobnodeid]
2. I have notifications 4.x dev installed, and the links for notifications/subscriptions seem to be appearing on the job_appln pages even though I haven't enabled notifications or subscriptions for that content type. I also tried to edit the job application to see if any settings were being enabled. However, it appears that even admins aren't allowed to edit nodes of the job application type.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | listing_jobappln.views_default.zip | 2.31 KB | NewZeal |
Comments
Comment #1
NewZeal commentedThanks for the issue.
1. Looks like that view got missed from listing_jobappln.views_default. Attached is the file with the view in it. You'll need to clear your cache once it is uploaded to install the new view.
2. The job application type is just like any other content type. When a user applies for a job, however, authorship of it transfers to the job owner. This means that the user no longer has access to the application and the job owner has full access. user/1 should still be able to access it as normal. For other roles to have access you need to set it in permissions. Having said that there may be some adjustments needed for good usability.
I do not think that the appearance of notifications links on the job application nodes would have anything to do with any listing modules. These are supplied by the notification module using hook_link.
Comment #2
NathanM commentedRegarding issue number 2, I just looked at my content queue, and it appears that job applications are not being created using the job_appln content type, or any other type, for that matter. They are nodes with blank content types. This might be related to what is causing the subscription links. As such, even user/1 can't edit those nodes.
Comment #3
NewZeal commentedOK. It appears that your job application content type was not created. Make sure that the job_appln content type exists. If not use content copy module to import it. You will need to view the file listing_jobappln/includes/job_appln-cck-type.txt in a text editor, copy it and import it at admin/content/types/import.
Comment #4
NathanM commentedThe job_appln content type does exist, in fact. However, there is an error when I try to enable the module caused by the fact that the content type already seems to exist. Enabling the job_appln module triggers the following messages:
The human-readable name Job Application is already taken.
* An error has occurred adding the content type job_appln.
Please check the errors displayed for more details.
* job application content type created
* The configuration options have been saved.
Comment #5
NathanM commentedOk, deleting the content type and re-enabling seems to have fixed issue number 2. Will upload the listing views file soon to try to take care of issue #1.
Comment #6
NewZeal commented