As soon as you see the “update to JobEngine version 1.1.7” prompt in the backend, please hit that button – right away. For this version, we solved some major issues related to multiple jobs in a payment plan and expiry dates.
Bug #590: On payment plans with multiple jobs, the second job is published Active even if the first job is still unpaid and unapproved.
When a job poster pays using Cash, the first job post displays “unpaid” and has to be approved by the admin (upon payment). Once approved, only then that the second and succeeding jobs included in the plan will be published active.
If the job poster publishes the first and second jobs in a row, the first post displays “unpaid” and the second one displays “pending.” If admin approves the second post, the first post remains non-active. The third and succeeding jobs will be published active upon posting.
Everything works the same as above when admin enabled “Pending Jobs” and job poster pays through Paypal or other payment gateways. If “Pending Jobs” is disabled, all jobs are posted active right away except when paid through Cash method.
On expiry dates, we have these changes:
Bug #591: All jobs not manually approved by admin do not get an expiration date.
Whether a job post is approved by admin or is posted active immediately on the site, it will now get an expiry date based on the payment plan.
Bug #624: When a pending job is approved from backend, it shows an expiry date that is more than the number of days stated in the plan.
This was because we set a default value of 30 days for jobs which expiration date field is left empty. We removed the default value to correct the issue.
Bug #593: Expiry Date doesn’t change after renewing a job.
Expiry dates are now renewed based on the selected payment plan.
Bug #592: When a job is approved from the backend, it goes back to Pending Jobs’ list when page is refreshed.
Now feel free to approve pending jobs from the backend: Engine Settings > Overview > Pending Jobs.
Other fixes for this version but minor ones –
Patch #502: The “Load More Jobs” button becomes visible before the jobs have loaded.
Bug #503: Setup Wizard: Payment plan does not allow values with cents
Bug #528: When a payment plan has multiple jobs and only one job to post remains, the plan reminder in the Dashboard is not displayed.
Bug #506: Move update setting into setting menu
Bug #508: Searching on the 404 page will get results from Google.
Bug #518: Loading screen overlaps the upper part
cool, but I dont understand:
“When a job poster pays using Cash, the first job post displays “unpaid” and has to be approved by the admin (upon payment). Once approved, only then that the second and succeeding jobs included in the plan will be published active.”
Shouldnt all jobs in in the plan have the UNPAID status and be published active, no matter what job is approved? that way its more clear to the admin and client that those jobs are not paid for yet + it makes it easier to approve/publish the jobs.
i think all jobs in a plan should be treated as part of that plan. i.e. it shouldnt matter which job I approve from the set of jobs already posted/waiting. users paid for the whole plan, and thus also all jobs they have been posting.
“If the job poster publishes the first and second jobs in a row, the first post displays “unpaid” and the second one displays “pending.” If admin approves the second post, the first post remains non-active. The third and succeeding jobs will be published active upon posting.”
1. doesnt this contradict the previous statement, which implies that the 1st job needs to be approved to have all jobs be published? its either ‘approve 1st, all published’ or ‘approve a job, that one + all other jobs posted after are published active”
2. say, a user buys a plan with 30 jobs in it and posts 20. If the admin only approves the last job, the first 19 are not published? the admin would have to manually approve all other 19 jobs? not very efficient, and a little confusion.
cool, but I dont understand:
“When a job poster pays using Cash, the first job post displays “unpaid” and has to be approved by the admin (upon payment). Once approved, only then that the second and succeeding jobs included in the plan will be published active.”
Shouldnt all jobs in in the plan have the UNPAID status and be published active, no matter what job is approved? that way its more clear to the admin and client that those jobs are not paid for yet + it makes it easier to approve/publish the jobs.
i think all jobs in a plan should be treated as part of that plan. i.e. it shouldnt matter which job I approve from the set of jobs already posted/waiting. users paid for the whole plan, and thus also all jobs they have been posting.
“If the job poster publishes the first and second jobs in a row, the first post displays “unpaid” and the second one displays “pending.” If admin approves the second post, the first post remains non-active. The third and succeeding jobs will be published active upon posting.”
1. doesnt this contradict the previous statement, which implies that the 1st job needs to be approved to have all jobs be published? its either ‘approve 1st, all published’ or ‘approve a job, that one + all other jobs posted after are published active”
2. say, a user buys a plan with 30 jobs in it and posts 20. If the admin only approves the last job, the first 19 are not published? the admin would have to manually approve all other 19 jobs? not very efficient, and a little confusing..
” If “Pending Jobs” is disabled, all jobs are posted active right away except when paid through Cash method.”
This is what I’ve been waiting for. To attract customers I’m having a “Free” job posting plan and I would never know when a job was pending until Iogged in. Sometimes it would be days before I checked only to see a pending job. If its “Free” that job should be posted immediately. Hopefully this works like I think it should. I’m so busy sometimes that I forget to check. Thanks again for the updates. Keep them coming!