Breaking: The map assets are built and moved 

Description 

The stylesheet and the script of the partner map are now compiled from sources in the repository, and both moved into a frontend/ subdirectory:

EXT:academic_partners/Resources/Public/Css/map.css
->  EXT:academic_partners/Resources/Public/Css/frontend/map.css

EXT:academic_partners/Resources/Public/JavaScript/map.js
->  EXT:academic_partners/Resources/Public/JavaScript/frontend/map.js
Copied!

The Leaflet library, its marker cluster plugin and their stylesheets keep their paths, and the map script still reads the LeafletObject global they define. All scripts are still loaded as classic scripts. Leaflet and the marker cluster plugin are built from their npm packages now, see Important: The map libraries are built from their packages.

Impact 

An installation that uses the extension as shipped needs to do nothing: the files are loaded by the extension itself, from the new location.

An installation that referenced the old path keeps pointing at a file that no longer exists.

Affected Installations 

Installations that override Templates/Partner/Map.html or reference map.css or map.js from their own site package.

Migration 

In an overridden template, add the frontend/ segment to the two references:

<f:asset.css identifier="partnerC2" href="EXT:academic_partners/Resources/Public/Css/frontend/map.css" />
<f:asset.script identifier="partnerS2" src="EXT:academic_partners/Resources/Public/JavaScript/frontend/map.js" />
Copied!

The four lines that load Leaflet and the marker cluster plugin stay as they are.