Hello,
there's an error in the location logic in Version 3.0.6
When using the plugin with a category set, the location repository tries finding locations matching those categories.
Now, tx_jobapplications_domain_model_location actually has the 'categories' field in the DB, but it isn't available in the backend.
Since the location repository will search against this field, the location search always has zero results and the location filter gets disabled in the frontend.
Actually it doesn't even make any sense. Why would one want to tie locations to categories? If you want the location filter to be dynamic like a fasset, it should be built using the locations that are bound to the result postings, just by going over them in a loop after the search in the controler.
For the time being I just shortened the findAll method in the location repository to:
$query = $this->createQuery();
$query->setOrderings([$orderBy => $order]);
return $query->execute();
At least that displays all locations for now.
Hope this helps,
Manuel
Hello,
there's an error in the location logic in Version 3.0.6
When using the plugin with a category set, the location repository tries finding locations matching those categories.
Now, tx_jobapplications_domain_model_location actually has the 'categories' field in the DB, but it isn't available in the backend.
Since the location repository will search against this field, the location search always has zero results and the location filter gets disabled in the frontend.
Actually it doesn't even make any sense. Why would one want to tie locations to categories? If you want the location filter to be dynamic like a fasset, it should be built using the locations that are bound to the result postings, just by going over them in a loop after the search in the controler.
For the time being I just shortened the findAll method in the location repository to:
At least that displays all locations for now.
Hope this helps,
Manuel