| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 3078101-8-allow-inheritance.patch | 1.89 KB | christianadamski |
| #6 | 3078101-6-allow-inheritance.patch | 1.89 KB | christianadamski |
| #3 | geolocation-3078101-2.patch | 1.18 KB | les lim |
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 3078101-8-allow-inheritance.patch | 1.89 KB | christianadamski |
| #6 | 3078101-6-allow-inheritance.patch | 1.89 KB | christianadamski |
| #3 | geolocation-3078101-2.patch | 1.18 KB | les lim |
Comments
Comment #2
les limThe ProximityField handler checks for the existence of a ProximityFilter on the view by looking for the a particular Plugin ID. That doesn't work out if we're using a custom handler that extends the ProximityFilter plugin.
Comment #3
les limPatch attached, which replaces the plugin ID-based string check with a "is_a()" call on the class type.
Comment #5
christianadamski commentedCould I kindly ask you to extend your patch to also include the same fix for ProximityFilter as well?
Comment #6
christianadamski commentedOk, that was a single line. Changed it myself.
Comment #7
christianadamski commentedAnd I just notice that your second check is wrong.
Comment #8
christianadamski commentedFixed patch
Comment #10
christianadamski commentedThanks!