Job regions as dropdown IS possible

Hi jobme,

here we go with some code:

filename: job-filters.php

<?php
/**
 *
 */

$s_categories 	= get_option( 'job_manager_enable_categories' ) && get_terms( 'job_listing_category' );
$s_regions 		= get_terms( 'job_listing_region' );
wp_enqueue_script( 'wp-job-manager-ajax-filters' );
?>

<form class="job_filters">

	<div class="search_jobs">
		<div class="row">
			<?php do_action( 'job_manager_job_filters_search_jobs_start', $atts ); ?>

			<div class="<?php echo $s_categories ? 'col-md-6 col-sm-6' : 'col-md-12 col-sm-12'; ?> col-xs-12 search_location">
				<label for="search_location"><?php _e( 'Location', 'jobify' ); ?></label>

				<div class="has-select">
					<div class="select">
						<select name="search_location" id="search_location">
							<option value="0" selected="selected">Alle regios</option>
							<?php foreach ( $s_regions as $region ) { ?>
							<option value="<?php echo $region->name; ?>"><?php echo $region->name; ?></option>
							<?php } ?>
						</select>
					</div>
				</div>

			</div>

I do think I am very close… Looking in the following file now:

wp-job-manager-functions.php (which is in the plugins/job-manager folder):

It is the get_job_listings function that does the actual search. Within this function on line 71 we can finde the following code:

// Location search - search geolocation data and location meta
	if ( $args['search_location'] ) {
		$location_post_ids = array_merge( $wpdb->get_col( $wpdb->prepare( "
		    SELECT DISTINCT post_id FROM {$wpdb->postmeta}
		    WHERE meta_key IN ( 'geolocation_city', 'geolocation_country_long', 'geolocation_country_short', 'geolocation_formatted_address', 'geolocation_state_long', 'geolocation_state_short', 'geolocation_street', 'geolocation_zipcode', '_job_location' )
		    AND meta_value LIKE '%%%s%%'
		", $args['search_location'] ) ), array( 0 ) );
	} else {
		$location_post_ids = array();
	}

I think this is where the actual matching of form input (search_location) and database job posts is done. I don’t know yet how to alter the query/code without breaking the whole search widget. Next on my todo is adding a variable search_region to the query. That way we can change the form input to search_region for the frontend and still keep the search_location option intact if we wanted to use it for the future. Will keep you posted on the progress of this one. Its a tricky one… 😉

If I read the query well (not that good in SQL) it matches the search_location to either the:

‘geolocation_city’,
‘geolocation_country_long’,
‘geolocation_country_short’,
‘geolocation_formatted_address’,
‘geolocation_state_long’,
‘geolocation_state_short’,
‘geolocation_street’,
‘geolocation_zipcode’,
‘_job_location’

I think thats why we can’t find regions with dashes. If you look at the geolocation_state_long in the CMS what will be matched is the english version of the state with a space as stated in the google api, or whatever api is used to get those geo-locations. So it matches the search_location input to this info in the db not the actual job_region.

I think the developer of Predefined Regions needs to rewrite this and make an actual relation between the joblisting post and the region, not just match the geo/job_location and the search_location.

Query update!!!!

SELECT DISTINCT * FROM wp_posts
		    WHERE ID IN (
		    	SELECT DISTINCT object_id FROM wp_term_relationships
		    	WHERE term_taxonomy_id IN(
				SELECT DISTINCT term_id FROM wp_terms
				    WHERE slug LIKE [search_region]
				)
			)
			AND post_status = 'publish'

This gives you the job_listings that comply to the search_region. I will alter the job-manager-functions.php and the plugin to add this functionality. When i’m done i will post this one!

Update! Check it out!

https://github.com/mrpharderwijk/wp-job-manager-regions-dropdown

I hope you as much fun with it as I do now ;)!!!!

Spaces are fixable, I think. Non-english characters will be a little bit more difficult I guess. Can you provide me the payload you send to the admin-ajax and the input in the database?