Regions

Geographic division — countries, regions, districts, towns. Used by the classifieds, the company catalogue and delivery.

Find them under Systém → Regiony.

Fields

Field	Note
Name	per language
Parent region	forms the tree
Is a country	marks the state level
Main	the default region
Active

Postcode, coordinates, and image are not entered anywhere

The region's database record has room for them, but the Systém → Regiony form has no such field — there is no way to set them through it.

The tree

Regions form a tree: country → region → district → municipality. They are moved by dragging.

A deeper tree is not necessarily better

A user choosing through four levels gives up. On a smaller site, countries and regions are enough.

Searching inherits downwards

Pick a region and the visitor also finds everything in its districts and municipalities. The same holds for saved searches.

Something classified only at region level is not found by someone searching a town

Inheritance works top-down, not the other way. So classify listings as low as possible.

\"Within X km of me\" search does not use the region's coordinates

Distance is computed from the address entered directly on the listing/company (geocoded via Google Maps), not from the coordinates of the region it belongs to.

Moving a region

Moving to the root of the tree is the riskiest operation

The whole structure is recalculated. On a large tree it takes a while; do not interrupt it, and go through the tree afterwards.

Deleting

The whole subtree goes with it

Delete a region and all its municipalities disappear — and with them the classification of everything in them. Disable an unused region instead.

Region versus payment region

They are not the same thing.

	Region	Payment region
Purpose	geographic classification of content	currency, payment options, document language and layout
Forms a tree	yes	no

You need both

The region says where a company is based. The payment region says what it can pay you with.