Jump to:
| Project: | Job Posting |
| Version: | 6.x-1.11 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | gmarus |
| Status: | postponed |
Issue Summary
I've created two jobs on my site and made a few updates to them after their creation. I have the Job Posting content type set to always create a new revision of the node on update but now it looks like each revision is showing up as a distinct entry in the job list. Strangely, this only happens on the job list page and not in the job list block.
I have confirmed that the number of times a job shows up in the page list is based on the number of revisions of the node.
I've attached a screen shot showing the block beside the page list to illustrate the problem.
This also seems to affect Views wherein selecting Job Posting nodes (without the Distinct flag selected) produces a list that includes all node revisions, not just the most recent version of the node.
I don't know a great deal about the database intricacies of Drupal but based on how core nodes are handled I think you should be putting Job Posting node revisions into a table separate from the one that contains the current version.
| Attachment | Size |
|---|---|
| Job Posting Revision Error Screen Shot | 30.66 KB |
Comments
#1
Thanks for the report. It shouldn't be necessary to create a new job_posting_revisions table (I believe revisions are stored at the 'node' level via 'node_revisions' table). I suspect the query needs some reworking in light of your report but it will be a couple of days before I can sit down and look at it. I'm a little surprised that I hadn't received a bug report like this until now but maybe you're just the first to say something. Thanks again.
#2
I am able to reproduce the problem and can confirm that additional nodes are being generated for each unique node revision IF you choose the 'create new revision' checkbox under the 'revision information' section on job_posting create/edit page. Changing the content through the revision information section without choosing the checkbox behaves as expected, otherwise you get duplicate nodes all sporting the job_posting specific data from the original.
It looks like you were correct in suggesting a new job_posting revisions table might need to be added because even though I can manipulate the queries for the job list page to eliminate the duplicates I can't obviously ensure the latest revision information, at least the job_posting specific fields, are present without storing this information somewhere (bit of a 'doh!' moment for me).
I'll leave this open until I can roll in a patch, hopefully in a week or so. Until then, you'll need to avoid the 'create new revision' checkbox feature or roll your own solution.
#3
I'm postponing this until D7 comes out and I port the module to that newer version
#4
I realize this is old, and it's possible it's been fixed(?) but I just want to mention that you can recreate this Jobs listing page w/ views and override the path so that it'll load the view you created instead of the default page that comes with the module.