shqipe420

As a matter of fact with the new update this issue does not occur anymore.

Again thanks for your help @bsfaradhy

Hi @bsfaradhy

Thanks for the heads up!

Alright then in case you are already aware of this issue and are working on this then it is fine. As I said it is only a matter of Lighthouse results issue and therefore not crucial, but nice if it would be fixed in the future.

If you think it’s gonna take some time to be fixed I would appreciate it if you have any idea how to use custom php/ JS Code to prevent this from causing the console error log.

Best Regards

Hey Jay,

Thanks for your reply.

Yeah thats exactly the issue I tried to tell you about, sorry in case it was not clear enough.

Meanwhile I also used a work around, where I insert a button in my WP admin backend Page, that clears the cache, when clicked on. Looks something like this:

// Create a button field for your submenu in your admin page
<form method="post" action="">

<?php
 wp_nonce_field('clear_cache_action', 'clear_cache_nonce');
?>

   <button type="submit" name="clear_job_cache_button" class="button">Empty Job Cache</button>
</form>

// Clear Cache
if (isset($_POST['clear_job_cache_button']) && check_admin_referer('clear_cache_action', 'clear_cache_nonce')) {

WP_Job_Manager_Cache_Helper::get_transient_version('get_job_listings', true);
wp_redirect(admin_url('YOUR_ADMIN_SUBMENU'));
exit;}

Looking forward to the update and thank you very much for your help again.

Hey Jay,

Regarding my initial issue I have found the cause: The Problem was the caching in the function get_job_listings() in wp_job_manager_functions.

As you mentioned, I tried to reproduce the error by deactivating all plugins except for WPJM and I used the theme twenty twenty one. You can reproduce the error by taking the following steps:

1. Enable the Option: Hide filled Positions
2. Create a Job and use the Backend option (not the Frontend or the edit-job in Backend as these update the whole post and clear the cache for job_listings) to fill the position by ticking the box next to the job and mark it as filled.
3. On the job page you will still see the job, although its design (contrast) is different from the other jobs (just as if the “hide filled positions” is disabled)
4. If you work on a localhost you can change the time settings of your computer and set it to a day after the currrent day. Now the job is not visible, as cached data is only used for 24 hours.

Btw. this also goes both ways: In case you set a job from not filled to filled by using this technique, the job is not going to be displayed.

In order to solve this issue I used the following code which disables caching:

function delete_cache_job_listings( $should_cache) {

	$should_cache = false;
	return $should_cache;

}
add_action( 'get_job_listings_cache_results', 'delete_cache_job_listings', 10, 1 )

However, as caching is important for the performance I would appreciate it if you could patch this or maybe show me another solution.

Thank you very much again!

Hey, thanks for your answer. Yes, I also use some custom code from my functions.php file. Yet for some reason when using my code to check if the job is filled, the job still shows up on the frontend, although the settings were set just like you mentioned. As I said it also worked, if you set the job to filled on the front or backend, but if you use a function which updates the database value for the meta key ‘_filled’ from 0 to 1 it doesn´t work.

Anyway, for anyone who is facing the same issue, here is a solution that worked for me: I modified the template “content-job-listing” with a conditional block which checks whether the job ID is filled or not. So you basically just add this code right before the template:

if(is_position_filled($post->ID) === false){
// The Rest of your template
}

I still didn’t figure out why it didn’t work without this code, but this works fine for me and I didn’t encounter any issues until now.