As you can see, 'Division' level is now added to WPL (also it is added to listing wizard, search widget, profile wizard etc):

To remove a location level, remove the location name in location settings.

You can remove any block if you like. You can also change their sorting pattern. If you remove a block, you are welcome to add it again in the future, but you cannot add any block out of the available blocks. Available blocks are the blocks that are included in default patterns.

Default patterns

Property: [street_no] [street][glue] [location4_name][glue] [location3_name][glue] [location2_name][glue] [zip_name]

User/Agent: [location5_name][glue][location4_name][glue][location3_name][glue][location2_name][glue] [zip_name]

Definitions

[glue]: Address separator, By default it is comma "," in WPL.

[location1_name]: Level 1 of your defined levels. By default it is country.

[location2_name]: Level 2 of your defined levels. By default it is state.

[location3_name]: Level 3 of your defined levels. By default it is county.

[location4_name]: Level 4 of your defined levels. By default it is city.

[location1_abbr]: Abbreviation name of level 1. By default abbreviation name of country.

[location2_abbr]: Abbreviation name of level 2. By default abbreviation name of state.

[zip_name]: zip code

Then search for your desired country and enable it. You can add new countries if needed as well but it is recommended to enable current countries instead of creating a new one.

Then click on "Load Next Level" to add second level locations (State/provinences etc.)

And add all of your second level locations.

You're finished! From now on, you can select a new country and its second level locations while adding/editing a property or from the search widget.

Since v4.2.0 “Hierarchical Dropdown” and “Hierarchical Multiple Dropdown” methods added for location field.

Then as you can see location placeholder changed on frontend of your website:

Note: It will suggest from previously added terms into WPL database.

WPL > Setting > Locations > Property Pattern > remove [location1_name]

If you want to remove the country name from user location you need to remove the [location1_name] from WPL > Setting > Locations > User Pattern.

You can set this in WPL Shortcode with "sf_multiplelocationtextsearch" parameter by using colon(:) as separator between multiiple location texts.

For example, you can use below shortcode in your page.

[WPL kind="0" tpl="default" sf_unit_price="260" sf_multiplelocationtextsearch="locationtext1:locationtext2:locationtext3" limit="12" wplorderby="p.mls_id+0" wplorder="DESC"]

For enabling/disabling countries, you can click on the "Show all countries" button to view all countries available.

By clicking on the '+' button near the top left of the screen, you can add new locations in the selected location level (country level, state level, city level, etc). For example, you can insert new countries in the country view and new states in the state view.

This issue happens because of the "ft_min_word_len" variable in your server's MySQL Configurations.
It's set to default value of 4, which ignores any word shorter than 4 characters.

You need to change this value to 2 so all your searches that contain values less than 4 letters work properly (like San Juan, Los Angeles, etc).
(Set it to a lesser value like 1 is not recommended, Because it may cause performance issues)

To do so (Root access to the server is required):

1- Edit your MySQL configuration at /etc/my.cnf and add the following line at the end of the file:
ft_min_word_len=2
(If the variable is already there, just change its value to 2)

Note: If your website is a Bitnami app, MySQL configuration file is on a different path:
/opt/bitnami/mysql/my.cnf

2- Restart MySQL server
on cPanel based servers:
sudo /scripts/restartsrv_mysql

On Bitnami stack:
sudo /opt/bitnami/ctlscript.sh restart mysql

on generic servers (You may need to use mariadb instead of mysql):
sudo service mysql restart

3- Confirm the value has changed with the following SQL command
SHOW VARIABLES LIKE 'ft_min_word_len';

4- Repair WPL properties table to rebuild the indexes:
REPAIR TABLE `wp_wpl_properties`
(If Wordpress's database prefix is different, make changes accordingly)

• The first API key used for frontend functions so you should restrict the key via domains because it's a public key and other users can see your key.
• The second one is Server Side API key. It is a private key used in the backend of WPL in server level so visitors of your website are not able to see it.