General - Miscellaneous

For settings that don't really belong anywhere else, don't warrant their own section, or that maybe aren't as impactful, they've been put into a 'Miscellaneous' section.

This is accessible by navigating to 'Property Hive > Settings > General > Miscellaneous':

Let's take a look at each setting individually:

If you have updated the search forms to include an 'Address Keyword' field where users can freetype a location search, this setting determines how this works.

If someone enters a search term we'll look at the property's address fields and return properties is a match is found. The options are:

Match Keyword Exactly - The entered search term must match the whole address field value. For example, if a search is done for 'London', properties with a street of 'London Road' WOULD NOT be returned as it isn't an exact match.

Perform Loose Search - The entered search term must partially match an address field value. For example, if a search is done for 'London', properties with a street of 'London Road' WOULD be returned as it isn't an exact match.

Search Within Location Perimeter - If someone searches for 'London' we'll make a request to the https://nominatim.openstreetmap.org API to get the boundaries of 'London' and properties within these bounds will be returned.

If you're storing commercial properties and you're entering top level properties and individual units (i.e. an office block AND individual offices) this setting determines how they show in search results on the frontend.

Still displaying old off market properties that have been sold, let or withdrawn can be good for SEO but we appreciate not everyone wants these to appear.

Though they won't directly be accessible through the frontend as we only ever show on market properties, they could still be accessed via Google or old mailouts and social links.

If an off market is viewed we'll display a warning accordingly:

However if you don't want these accessible at all, you can opt to redirect users to the search results page if preferred by changing this setting.

Bullet points by default are freetype features on a property record:

Should you wish for this list to be a fixed list instead you can choose 'Select From A Predefined List'. This will make the features a list of checkboxes to choose from instead:

With this enabled the features available to select here can be customised as custom fields under 'Property Hive > Settings > Custom Fields > Property Features'.

If entering properties manually into Property Hive and not importing them from a third party CRM you can opt for the reference number, used internally as your own identifier, to auto-increment when adding a new property.

With this enabled you'll have the option to set your starting reference number:

When creating a new property this will then be set by default:

Enable this if you are wanting to allow applicants to login after registering their details. When using the  [applicant_registration_form] shortcode, a password box will also be shown allowing them to create an account.

By logging in, applicants will have the ability to edit their details and requirements, view any viewings they're attending, and see any properties they've shortlisted if using our Property Shortlist add on.

Enable this if you wish to receive an email when someone registers. This can be useful should you wish to respond accordingly and to contact the applicant to further qualify them in a timely manner.

If you're allowing applicants to login you'll need to create pages for the above four pages and then select them from the list above.

Each of the pages created should contain the associated shortcode shown in the tooltips.

If you're using Property Hive to automatically send matching properties to applicants these lower and higher percentages will be used to help determine how matching on price is effected.

We know that if someone is searching for a property up to a certain value, they could probably stretch a little further should the perfect property come along. Likewise, if someone is searching for up to £500,000, they probably don't want properties less than £400,000.

Use this setting to configure the default lower and upper boundaries of the price budget entered.

Note that these upper and lower match prices can also be overridden on per-applicant basis in their requirements:

When entering an applicants requirements, either manually in the backend of Property Hive, or if they're registering themselves on the frontend, this determines how locations are stored.

As you have probably already noticed, we keep making Property Hive better, adding new features and improving and building upon the current features.

To do that, we try to learn from our users what works, what doesn’t, what can be optimised, and how much usage certain features are getting so we can best spend our limited time wisely.

With this ticked you'll help us build a better product but sending us the following information:

This is the information that is sent to us:

• License key
• URL
• PHP version
• WordPress version
• Server software
• Property Hive version
• Property Hive install date
• Admin email address (won't ever be shared or used for marketing purposes)
• WordPress settings (multisite, language, theme, plugins)
• Property import formats being used when the Property Import add on is in place
• How many of each post type you have