TerraSuite – Estate Agency Software, Property Listings and Map Search

변경이력

1.1.1

• A property’s UPRN is now shown on its page. The field was added in 1.1.0 and
  collected on every property, but no template printed it, so nobody outside
  the editing screen ever saw one. It now sits with the other identifiers,
  beside the reference and the MLS number, rather than among the disclosures.
• Each country is now only asked for its own paperwork. The seven Spanish
  rental disclosure fields, and the IBI and refuse charge, were being offered
  on properties in Portugal, Italy and France, which have no reference rent
  index, no gran tenedor and no IBI. The five British fields – UPRN, council
  tax band, coalfield and the two EPC ratings – were being offered in Ireland,
  which uses neither council tax nor an EPC. The fields each country does need
  are unchanged.
• Getting Started now covers every screen in the plugin. Two were missing, both
  of them Featured email: the screen itself and its settings tab. The guide is
  also checked the other way round, so a step can no longer claim it covers a
  screen that does not exist – one step did, and read as coverage.
• The SSH host key help on the import screen is one sentence shorter and says
  what to type. Spanish is complete, at 2,493 of 2,493 strings.

1.1.0

• Spanish rental adverts now carry what the law requires. Real Decreto-ley
  29/2026 came into force on 8 October 2026 and names what every rental offer
  must publish: the reference rent index where the home is in a declared
  rent-controlled zone, the applicable rent limit together with the rules that
  set it, the unit’s registration code where it has one, and whether the
  landlord is a gran tenedor. Seven new fields hold all of it. The
  rent-controlled designation is made by town, not by property, so it is
  answered once on the Location term and every property in that town inherits
  it, with an override for a municipality declared only in part. There is no
  switch to turn the fields on: each one publishes as soon as it holds a value,
  and a notice above the title names anything still missing where the zone says
  it is required.
• A feed from another agency is now recognised as another agency’s stock. If
  you import a partner’s feed, the properties used to be recorded as your own
  instructions. The listing address inside the feed says whose they really are,
  so they are now marked as shared and attributed, with nothing to set up and
  no question to answer.
• Sixty fields that no import or export could reach are now carried by both.
  Eleven of these were fixed on 11 October; the rest were found by listing
  every field the plugin registers and comparing it against what the import
  mapping screen and the CSV export actually offer, which is now checked
  automatically so it cannot drift again.
• UK properties have a UPRN field. The local authority gives every addressable
  property in Great Britain a UPRN, it stays with the building through a
  renumbering or a conversion into flats, it is printed on every EPC, and Land
  Registry has published it alongside Price Paid Data since August 2026. You
  type it off the certificate; there is no lookup, because the address-to-UPRN
  mapping is licensed.
• The Spanish translation now travels with the plugin. It used to be installed
  separately on each site, which meant no update ever carried it and the
  deployed copy was three weeks behind the plugin, so new screens appeared in
  English on a Spanish site. The catalogue is built into the plugin and is
  rebuilt as part of every release.
• Getting Started is the first item in the TerraSuite menu. It was two thirds
  of the way down, below Settings, which is a poor place for the screen written
  for your first morning.
• Content packs now download. The area guides and photographs are fetched from
  our own website, and our firewall was blocking that request for every
  installation since launch; the plugin reported it as “forbidden”. The fix is
  on our side and this version needs no change for it, but this is the first
  release since it was put right.
• The import screen now reads the file you uploaded. Instead of forty empty
  boxes asking you to type your own column names from memory, each field
  offers a list of the columns your file really contains, with a match already
  chosen where one is obvious, and three rows of that column shown beside it
  so you can see what you are about to import. Columns nothing is reading are
  named underneath.
• Eleven more fields can be mapped on an import and are carried by the CSV
  export: your own reference, year built, furnished, parking, garden, tenure,
  council tax band, community fees, IBI, and the two energy values in kWh and
  kg CO2. The import has always been able to write them; nothing could ever
  send them, because the mapping screen offers only the fields listed here.
• The CSV export no longer carries four columns that could never hold
  anything, and now fills three that were always blank: the first address
  line, the source’s last-modified date and the source listing URL.
• A property’s own reference now survives an export and re-import. The
  reference column used to be overwritten with a WordPress post id, which
  means nothing on another site, so an agency’s quotable references were lost
  in a move.

1.0.3

• A column in an imported CSV reading “No”, “false” or “off” is now stored as
  no. It was stored as YES, because the test asked whether the cell was empty
  and those words are not. An agency importing its own stock got a swimming
  pool and a garden on every property. “0” worked only by accident.
• An empty price, bedroom or area column in an imported CSV now leaves the
  field empty instead of setting it to zero, so a property with no price is no
  longer published at nothing.
• The “defaults for missing values” on the import screen – currency, country
  and department – now apply to a CSV source. They were read by the XML and
  JSON importers and ignored by the CSV one, while the screen warned that a
  feed with no currency turns 300,000 euros into 300,000 pounds.
• The directory listing is now titled “TerraSuite – Estate Agency Software,
  Property Listings and Map Search” rather than “TerraSuite”. Nothing about the
  plugin changes: the slug, the brand and the name WordPress shows on your
  Plugins screen are all the same. WordPress.org weights the listing title
  heavily when it ranks a search, and every plugin above us for “real estate
  plugin” and “property listings” carries those words in its name.
• An agency can now say which departments it runs. A sales-only agency switches
  lettings off and the other way round, and whatever is unticked stops
  appearing on the search form, the property editor, the import mapper and the
  registration form. A department cannot be switched off while properties are
  recorded against it, and the message says how many.

1.0.2

• The property, article, area guide, team, review and service post types, and
  the eight taxonomies with them, are now prefixed terrasuite_ rather than ts_.
  Existing records are carried across on upgrade; no address changes.
• The printed particulars sheet loads its stylesheet the WordPress way instead
  of printing it into the page.
• Every value a form sends is sanitised where it is read: prices and sizes, the
  areas drawn on the map, the term lists, client notes, import separators and
  stored credentials.
• The valuation estimate is escaped where it is output rather than where it is
  built, because a filter can change it in between.
• The knowledgebase is no longer part of the free plugin. Writing and publishing
  articles is a TerraSuite Pro feature; nothing already written is removed.
• Search results no longer repeat a property across two pages when several share
  the same price or date.
• Spanish, and any other translation, is read from wp-content/languages/plugins
  as WordPress.org supplies it.

1.0.1

• Drawing an area on the map, and shortlists, are now part of the free plugin.
• The shortlist has its page back. Properties could be saved with the heart
  but there was nowhere to see the list again.
• Help articles can be written and published here. The screen for them was
  missing, which left the /help page with no way to put anything on it.
• QR codes, and the ready-written articles, moved to TerraSuite Pro.
• No page is created for a feature that is not installed.
• Opening Get Content no longer contacts us. The list of regions is fetched
  when you ask for it, which is what that screen always said.
• Stored passwords, and the tokens in feed addresses, use a key belonging to
  this plugin. They were derived from the WordPress authentication salts, so
  rotating those after a security incident destroyed them with no warning.
• Feed passwords are stored with AES-256-CBC rather than a reversible scramble.
• A downloaded content pack is refused if it contains anything runnable.
• Every external service the plugin can reach is now listed above.

1.0.0

• First release.