Skip to content
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

Mandatory field marking and validation for the geo range search in the geoPosition field on the website #922

Open
3 tasks done
fredericalpers opened this issue Oct 8, 2024 · 3 comments · May be fixed by #934
Open
3 tasks done
Assignees
Labels
component: property list Issue, Pull Request or Discussion related to property lists QA Issue or Pull request that is in review UI/UX Issue, Pull Request or Discussion related to UI/UX

Comments

@fredericalpers
Copy link
Member

fredericalpers commented Oct 8, 2024

Mandatory field marking and validation for the geo range search in the geoPosition field on the website

Introduction

There are some mandatory fields for the geoPositions field. These include country, radius and at least city or zip code. These mandatory fields are not declared and marked as mandatory fields in the frontend.

User Story

We currently use the onOffice for WP-Websites plugin to display properties on our website. A central feature of our website is the geo range search in the geoPosition field, which allows visitors to search for properties based on location information. However, there is a problem: although the fields “Country”, “Radius”, “City” and “Postcode” are defined as mandatory fields in the backend, this is not displayed correctly in the frontend. Users can leave the fields empty without being informed about missing entries, which leads to incomplete search queries.

In order for the geo range search to function optimally and for users to provide complete and accurate information, the relevant fields must be marked as mandatory fields and also be validated correctly in the frontend.

As a real estate agent, I would like the fields “Country”, “Radius”, “City” and “Postcode” in the geolocation field of the radius search to be marked with an asterix "*" as mandatory fields and displayed and validated accordingly in the frontend so that users can fill in this information correctly and completely.

Improving the geo range search by marking mandatory fields is crucial for the user-friendliness and success of the property search on the website.

Task / Requirements

  • The fields country, radius, city and zip code in the geoposition field of the radius search should be clearly marked as mandatory fields in the frontend. Each of these fields should be marked with an asterisk (*) to indicate that it is a mandatory field.
  • If one of the mandatory fields remains empty, the search query may not be sent.
  • An error message must be displayed informing the user that the mandatory field must be completed.
@fredericalpers fredericalpers added UI/UX Issue, Pull Request or Discussion related to UI/UX component: property list Issue, Pull Request or Discussion related to property lists labels Oct 8, 2024
@fredericalpers fredericalpers added this to the v5.8 milestone Oct 8, 2024
@yeneastgate yeneastgate self-assigned this Oct 16, 2024
@yeneastgate
Copy link
Contributor

@fredericalpers I would like to confirm some points with you

  • The fields country, area, city and zip code in the geoposition field of the area search should be clearly marked as mandatory fields in the frontend.

=> When you refer to the "area" field, do you mean the "radius" field?

mandatory.field.mp4

Note: If the fields “Country”, “Area”, “City” and “Postcode” are defined as mandatory fields in the backend, will all four fields become mandatory in the frontend? This means that old users who had previously checked all four fields in the admin will no longer be able to search by just three fields in the frontend.

@fredericalpers
Copy link
Member Author

@yeneastgate Thank you I updated it to "radius" instead of area.

The fields country, radius, city and zip code in the geoposition field of the radius search should be clearly marked as mandatory fields in the frontend by using the asterix "*".

@yeneastgate
Copy link
Contributor

@fredericalpers I've created PR for this issue. Please help us review it. Thanks!

@fredericalpers fredericalpers added the QA Issue or Pull request that is in review label Oct 18, 2024
@fredericalpers fredericalpers removed this from the v5.8 milestone Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: property list Issue, Pull Request or Discussion related to property lists QA Issue or Pull request that is in review UI/UX Issue, Pull Request or Discussion related to UI/UX
Projects
None yet
2 participants