Sitemap
- What does it do?
- Installation
- Upgrade
- For integrators
- Configuration
- Styling
- For developers
- Known problems
-
ChangeLog v3
-
3.0 Changes
- Breaking: Partner pages render their content without a global path
- Breaking: The map script is a module
- Breaking: Images render as a responsive picture
- Breaking: The page description is an exclude field again
- Breaking: The partner controller is final
- Breaking: The partner map ships no stylesheet
- Breaking: Partner pages render inside the site layout
- Breaking: The partner repository declares what it returns
- Breaking: Icons are renamed and follow the colour scheme
- Breaking: Removed TYPO3 v12 support
- Breaking: Partner templates carry speaking classes
- Feature: Active filter tags, a reset link and a result count
- Feature: The partners group has a title and an icon
- Feature: The partner map is configurable per site
- Feature: Partner filter selections have a URL
- Feature: The script of the partner map can be switched off
- Feature: Change the partner list and map by event
- Feature: Route enhancers for the partner list and map
- Feature: Own category types are named by their title
- Feature: The partner list can be paginated
- Feature: The plugins can render the content element header
- Feature: The plugins dispatch the plugin view event
- Deprecation: The classic files of the map libraries
- Important: Category type icons come from the frontend icon registry
- Important: Content elements have new titles and descriptions
- Important: A filter keeps the default categories of other types
- Important: The FlexForm data structures moved
- Important: The list demand is not part of the cache hash
- Important: TYPO3 13.4.35 or 14.3.7 is required
- Important: The link of a link page keeps its definition on TYPO3 v14
- Important: The page type is registered from a boot listener
- Important: The map partial skips a partner it must not draw
- Important: The partner map loads its libraries as modules
- Important: Partnerships keep their page and role when either is published
- Important: Roles list their partnerships of the default language
- Important: Sorting options read the plugin override on TYPO3 v14
- 3.x Changes by type
-
3.0 Changes
-
ChangeLog v2
-
2.4 Changes
- Breaking: The map assets are built and moved
- Breaking: Removed the unused autocomplete library
- Breaking: Site sets and static templates have been restructured
- Feature: Choose, order and label the partner filters
- Feature: "Show hidden records" plugin option for the partner lists
- Important: The development branch installs as 2.4.x-dev
- Important: The category filter accepts a list of uids
- Important: The category tree offers the categories of the group
- Important: The description of Default categories names their rule
- Important: Extended PartnerDemand and demand handling
- Important: The filter form works under a security policy
- Important: Label overrides of the filters are read from the plugin path
- Important: The geocoding command identifies the site
- Important: A hidden part of the form keeps the preset value
- Important: An incomplete default sorting keeps the default
- Important: Label overrides are read from the documented path
- Important: The map shows only partners with a location
- Important: The link column of pages is nullable now
- Important: The page module shows the page categories
- Important: The page template name of the academic partner page type is set explicitly
- Important: The partner map draws when its script loads late
- Important: The partner map honours "Show on map"
- Important: The map libraries are built from their packages
- Important: The partner map skips partners without coordinates
- Important: The partner map allows its tiles under a security policy
- Important: Partner page reads the page record from page
- Important: The partner page type renders its categories
- Important: Partner queries are ordered deterministically
- Important: A partner role sorts its partnerships on its own
- Important: The partner select is sorted by label
- Important: The partner select offers hidden partners
- Important: Each partnership renders once per language
- Important: Partnerships without a role are listed too
- Important: Translations of partnerships keep their parent
- Important: A sorting submitted as a list is ignored
- Important: The sorting select shares the option rendering
- Important: The static template and the backend layout are registered correctly
- Important: Translated partnerships keep their role
- 2.3 Changes
- 2.2 Changes
- 2.1 Changes
- 2.0 Changes
- 2.x Changes by type
-
2.4 Changes