---
title: "Feature: The plugins dispatch the plugin view event"
manual: "Academic Partners"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-partners:feature-plugin-view-event@main"
source: "Changelog/3.0/Feature-PluginViewEvent.rst"
rendered: "2026-10-26T19:20:19+00:00"
---

# Feature: The plugins dispatch the plugin view event {#feature-plugin-view-event}

## Description {#description}

The partner list, the partner map, the partnerships list and the partnerships
teaser of **academic_partners** dispatch
`\FGTCLB\AcademicBase\Event\ModifyPluginViewEvent` of
**academic_base**, once each time they render, after assigning their
own variables. A listener adds a variable to their templates without replacing
the controller.

The context of the event names the extension `AcademicPartners` and the
plugin names `List`, `Map`, `PartnershipsList` and
`PartnershipsTeaser`, which a listener checks for the plugin it means.

The partner list and map dispatch it after their list event,
`ModifyPartnerListEvent`, which stays.

The event, with an example listener, is described in the [changelog of
academic_base](https://docs.typo3.org/p/fgtclb/academic-base/main/en-us/Changelog/3.0/Feature-ModifyPluginViewEvent.html#feature-modify-plugin-view-event).
What the content elements of this extension pass in is described in
[ModifyPluginViewEvent](https://docs.typo3.org/permalink/fgtclb/academic-partners:developers-event-modify-plugin-view-event@main).

## Impact {#impact}

A project adds a variable to the templates of these plugins with an event
listener instead of a subclass or a copy of the controller. The behaviour is
the same on TYPO3 v13 and v14.
