-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pro search {pro_search_distance} can't return 0 #3245
Labels
Bug: Accepted
Bug has been confirmed, is reproducible, and ready to work on.
Comments
This appears to be an issue with the parser in general, not Pro Variables in particular. Elvis can be dangerous! (when you're using Elvis operand |
intoeetive
added a commit
that referenced
this issue
Apr 11, 2023
intoeetive
added a commit
that referenced
this issue
Apr 11, 2023
intoeetive
added a commit
that referenced
this issue
Apr 24, 2023
intoeetive
added a commit
that referenced
this issue
Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
EE 7.2.13
The {pro_search_distance} should show the distance from the 'to' lat/longitude parameter, and it works UNLESS the distance is 0. Then it just is empty. I couldn't get it to output 0 no matter how I futzed around with it, including just hard coding '0' in the code.
I'm not sure how to fix, but it's definitely a bit confusing. And at some point in the past, it did work.
Example template:
I had 2 custom fields local_lat and local_long - local_lat 52.163298 local_long 4.505543 is so close, rounded it comes to 0 and just doesn't display anything for that variable.
The text was updated successfully, but these errors were encountered: