ModifyPluginViewEvent 

When it is dispatched 

Both content elements dispatch the event once per rendering, from ProjectController::listAction() , after ModifyProjectListEvent and after the action assigned its own variables:

getControllerExtensionName() returns AcademicProjects for both. A submission of the filter form is answered with a redirect and renders nothing, so it dispatches no event. The project page is no plugin and dispatches no event.

What this extension passes in 

The view holds these variables when the event fires: projects , demand , categories , filterTypes , visitorSelection , data (the content element record as an array), record and the settings . A listener that assigns one of them again replaces it in the templates.

getSettings() of the context returns the settings of the content element merged over plugin.tx_academicprojects.settings , the values of the site settings included.

Example 

A site places a Selected Projects element on each project page to show related projects, and wants the card of the project the visitor is on to look different, or to be left out. The listener hands the uid of the page being rendered to the view:

<?php

declare(strict_types=1);

namespace MyVendor\MyExtension\EventListener;

use FGTCLB\AcademicBase\Event\ModifyPluginViewEvent;
use TYPO3\CMS\Core\Attribute\AsEventListener;
use TYPO3\CMS\Frontend\Page\PageInformation;

final class AddCurrentPageToSelectedProjects
{
    #[AsEventListener(identifier: 'my-extension/add-current-page-to-selected-projects')]
    public function __invoke(ModifyPluginViewEvent $event): void
    {
        $context = $event->getPluginControllerActionContext();
        if ($context->getControllerExtensionName() !== 'AcademicProjects'
            || $context->getPluginName() !== 'ProjectListSingle'
        ) {
            return;
        }
        $pageInformation = $context->getRequest()->getAttribute('frontend.page.information');
        if ($pageInformation instanceof PageInformation) {
            $event->getView()->assign('currentPageUid', $pageInformation->getId());
        }
    }
}

An override of Project/Item.html compares {project.uid} with {currentPageUid} . Both are uids of the default language, on a translated page as well.

Rules and pitfalls 

• The event fires for the plugins of seven academic extensions. Check the extension name and the plugin name before acting, as the example does.
• A variable the action assigned is replaced only in the view. The query has run already: projects a listener assigns as projects are rendered, but the filter keeps offering the categories of the queried projects. A change of which projects are shown belongs in ModifyProjectDemandEvent or ModifyProjectListEvent.

Introduced in 

• Feature: The plugins dispatch the plugin view event made both content elements dispatch the event in 3.0.
• Breaking: The project controller is final made the controller final, which leaves the events as the way to add view variables.
• The event itself was introduced by fgtclb/academic-base:feature-modify-plugin-view-event.