- This topic has 2 replies, 1 voice, and was last updated 3 years, 5 months ago by
.
-
Posts
-
I have to manually renew some postings for companies that have a contract with us. When they expire, I manually change the expiry date.
I renewed the postings by updating the posting and expiry date and published them. However, the published posting somehow did not register the new expiry date, so while it is displayed on the website, it has a "job expired" note and the posting date is June 1-May 29 instead of June 1-Aug 31 that I entered in on the backend.
https://locums.ca/jobs/medecin-de-famille-qc-digital-healthcare-new/
https://locums.ca/jobs/family-physician-bc-digital-healthcare-new/
https://locums.ca/jobs/family-physician-sk-digital-healthcare-new/It happened last time as well and I think we ended up having to recreate new postings. We've been manually creating new postings, but this is not sustainable. How do I change the expiry and posting dates if not by manually changing those fields in the backend of the site?
For the time being, I've just added display: none; to the elements I don't want shown to users, but this is simply a workaround and doesn't solve the issue. The dates in the header are still incorrect and inconsistent with what has been entered in the backend.
Here's the CSS I've added to hide the erroneous information. Please remove it when you're debugging the issue.
.job-action .noo-message-error, .job-message-job-status .jm-status-job-expired {
display: none;
}
You must be logged in and have valid license to reply to this topic.