If you have a view that has both the State/Province field and a Proximity search as exposed filters. The State/Province field does not detect changes in the Proximity Country field and thus returns invalid results for countries other than the default country.

I'll attach a patch shortly that resolves this issue by making the province field aware of the Proximity field.

Comments

shawn_smiley’s picture

Status: Active » Needs review
StatusFileSize
new2.94 KB

Here is the patch to fix this issue.

The patch does two things:
1. Adds the class 'location_auto_country' to the Proximity Country field.
2. Updates the grovel_country() method to check for the Proximity Country field in addition to the Country field.

podarok’s picture

Status: Needs review » Active

#1931088: [META] Fixing tests tests were broken, so triggering to active

podarok’s picture

Status: Active » Needs review

bot

podarok’s picture

Status: Needs review » Fixed

#1 commited pushed to 7.x-3.x
thanks!!!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.