jonryan

Thanks for reporting this!

@paul_lenk I’m not sure what is happening here. Somehow the initial XHR request is canceled and then a second one is made. My assumption here is this is likely due to your theme. You might want to try switching to a default WP theme to see if the issues goes away.

@dievernon for 1) I think you are missing the [‘job’] as the first array element.

2) what you want to do here is actually pretty simple and can be one of two ways. You can edit the file here where it checks the string length: https://github.com/Automattic/WP-Job-Manager/blob/d1341dd2900c81ad8de0bf67bbc6afef126ea28f/wp-job-manager-template.php#L571

The better way is to use a filter, and you can use the_company_name. You’d essentially want to make a filter that does the above, checking the string length and if it’s zero returning “company name withheld”.

good luck!

@reluctantdeveloper did you check to make sure the code is still in your functions.php file? There were some minor changes to the geocoding but I’m not sure why that would impact this. I’ll see if I can find out.

Sorry just to clarify here:

“If you look at ‘All Jobs’ overview you can see the correct date displayed. But, if you click back into the listing the old date will still appear. When you re-load the page you can see the correct timestamp, but it loads the incorrect date.”

Is this in the backend or using the jobs shortcode in the front? Also can you clarify what you mean when you say the timestamp is correct, but not that data?

I think there is some confusion in posting jobs typically, in that people use the backend interface, when really the frontend one should be used.

@csrjobs can you try deactivating your plugins? You have a selector conflict I believe.

Depending on your theme it could be possible the theme is reversing the buttons, it’s hard to say. If you inspect the XHR request in the dev console when you press the button triggering a state change, what do you see for the search query? By inspecting this you can figure out if this is a frontend or backend issue.

@robertmerrill take a look at this, the question shows how to do this. Basically you need to add the custom post type to the archive file using a hook.

https://wordpress.stackexchange.com/questions/179023/adding-custom-post-types-to-archive-php