---
title: "Important: The map shows only partners with a location"
manual: "Academic Partners"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-partners:important-map-shows-only-located-partners@main"
source: "Changelog/2.4/Important-MapShowsOnlyLocatedPartners.rst"
rendered: "2026-10-26T19:20:19+00:00"
---

# Important: The map shows only partners with a location {#important-map-shows-only-located-partners}

## Description {#description}

A partner page whose geocoding never ran, or failed, was drawn on the map at
0/0, in the open ocean south of Ghana, instead of being left out.

`PartnerController::mapAction()` fed the map from
`PartnerRepository::findByDemand()`, which carried no geocode constraint,
so such a record reached the template. `\Domain\Model\Partner` types both
coordinates as non-nullable `float` defaulting to `0`, so a missing
value arrived there as a valid one and rendered as
`data-lat="0" data-lng="0"`.

Four things changed:

-   The map query requires both coordinates. **The list is unchanged**: a
    partner without coordinates is still a perfectly good list entry.
-   With nothing left to draw, the plugin renders a message instead of an empty
    map centred on Germany, and the Leaflet assets are no longer loaded for a
    map that is not there.
-   `Partner::isDrawable()`, `{partner.drawable}` in Fluid, is the
    same rule for a template that renders one partner rather than a query
    result, a detail page drawing the partner's own location for example.
    `Partner::isShownOnMap()` applies this rule together with
    **Show on map**, see [Important: The partner map honours "Show on map"](https://docs.typo3.org/permalink/fgtclb/academic-partners:important-partner-map-honours-show-on-map@main).
-   The coordinate columns are synchronized with the default language record
    now (`allowLanguageSynchronization`). A place does not move when the
    page is translated, and a partner translated before geocoding ran kept an
    empty coordinate and was drawn at 0/0 in that language.

**Absence is the criterion, not the value.** `NULL` and the empty string
mean "no coordinate". A stored `0` is a real one, and only the pair 0/0 is
refused. Longitude 0 runs through the United Kingdom, France, Spain and Ghana,
and latitude 0 is the equator, so treating a single zero as missing would hide
partners that are genuinely there.

## Impact {#impact}

Synchronization acts on the write path only, so it repairs nothing that is
already stored. The upgrade wizard
**Synchronize academic partner pages with their translations**
(`academicPartners_synchronizePartnerTranslations`) does that once for
existing records, for the coordinates and for the switch
**Show on map**. It leaves alone a translation whose coordinates the
editor detached deliberately, as well as deleted records and workspace
versions.

`GeocodeCommand` writes through the DataHandler now rather than through the
repository, because only a DataHandler write runs the synchronization. A write
the DataHandler refuses fails the command, where it previously passed silently.
The queue selects on `geocode_status = 'open'`, so a result that never
reached the database would be retried on every scheduled run.

## Affected Installations {#affected-installations}

Every installation that renders the partner map plugin.

An installation that replaced [`Resources/Private/Templates/Partner/Map.html`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Resources/Private/Index.html#file-extension-resources-private-templates-controllername-actionname-fluid-html)
keeps its own copy and gets neither the message nor the conditional assets. The
query change reaches it regardless.

## Migration {#migration}

Run the upgrade wizard once after updating, in
**Admin Tools > Upgrade > Upgrade Wizard** or on the command line:

```bash
vendor/bin/typo3 upgrade:run academicPartners_synchronizePartnerTranslations
```

> [!NOTE]
> The pair 0/0 is matched as a string, in the spelling the geocoding command
> writes, because a numeric comparison is not portable while the column is
> `VARCHAR(20)`. A hand-entered `0.0` therefore reaches the
> frontend, which drops it, see
> [Important: The partner map skips partners without coordinates](https://docs.typo3.org/permalink/fgtclb/academic-partners:important-partner-map-skips-partners-without-coordinates@main).