Make hiding expired job posting a configuration option
ij - October 11, 2008 - 10:59
| Project: | Job Posting |
| Version: | 5.x-1.4 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi!
I read that there was one or the other question for the job posting module how to hide expired job postings from being displayed.
Your point was that it would be better to show a closed job posting than a 404 page when the job would be deleted from the database after expiration.
Would it be possible to just exclude those expired postings from being listed in the block and other lists? Something like "select jobs from jobpostings where hidden_flag is not 'true'"?
Maybe this can be either configurable by only the admin or by every user/job posting.
Would be nice!
Keep on the good work! :-)
#1
Expired postings are already by design excluded from the built-in job posting list page and block (but not from custom views, etc.). At that point the listings are still viewable as end nodes and displayed 'read-only' (without an application link and a deadline field that reads 'closed').
Perhaps I've misunderstood you, but I'm not sure what you're asking for beyond what's already supplied...
#2
Exactly: the expired nodes are marked as closed, but I would prefer if those won't get listed on the list page (or front page) nor in the block. At least that's what is happing on my site. The expired nodes are still listed in the job posting block, the front page and the list page (../jobs).
See http://www.sysadmin-jobs.de/jobs for an example.
But maybe that's just a bug? I'm using Drupal 5.10 on Debian Etch with Mysql 5 and Job Posting module 5.x-1.4. Or might it be related to comments and fivestar module being allowed, so they keep the expired job posting nodes open instead of being hidden?
#3
I'll look into this but unfortunately we're starting a holiday weekend in my part of the world and I won't get around to looking at this for at a couple of days since I'll be out-of-town. In the meantime feel free to report any additional observations that may be pertinent and I'll try to check back when I can.
#4
After testing with fresh installs of Drupal-5.11 and job_posting-5.x-1.4 neither the built-in block nor list at '/jobs' show expired nodes so I can't seem to reproduce the problem you report.
Are you using custom views or the default 'to front page' node setting? In either of these scenarios the custom SQL that automatically excludes expired nodes on the module block and list display is not applicable...
#5
Hmmm, with a fresh install of drupal 5.11 and the database as well, I can updated entries (see other issue report), but closed job postings are still listed on the front page. They are not listing under /jobs/ or in the job posting block, though. That's great, although I don't know why it didn't work as expected (and documented) in my previous test.
Would it be possible to exclude closed job postings from being posted to front page as well?
#6
You can easily stop ALL job postings from going to your front page by unchecking the 'promote to front page' box (and/or setting it to be unchecked by default under 'content types') on the node creation form but I'm not sure how best to go about adding the conditional logic to the node module itself. You'd probably want to use 'views' for this, I imagine...
Unless your business rules dictate otherwise I'd go the simple route of just making '/jobs' my 'default front page' using the form input on 'site information' page and let it handle the node listing's visibility.
#7