Result of testing the release candidate for glpi v11

[xigulor]

Hello,

I've tested the release candidate for glpi 11 :

• Installation ok. Replaced the folder in the marketplace folder, glpi asked me to update and enable it, all ok.
• The plugins seems working, but I have those messages in the logs when I access the setup page :

[2025-11-19 09:52:40] glpi.WARNING: *** User Warning: The output buffer has been unexpectedly closed in ./marketplace/ticketfilter/front/filterpattern.php. at LegacyFileLoadController.php line 68
Backtrace :
...Glpi/Controller/LegacyFileLoadController.php:68
./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\Controller\LegacyFileLoadController->__invoke()
./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\Component\HttpKernel\HttpKernel->handleRaw()
./vendor/symfony/http-kernel/Kernel.php:197 Symfony\Component\HttpKernel\HttpKernel->handle()
./public/index.php:70 Symfony\Component\HttpKernel\Kernel->handle()

[2025-11-19 09:52:40] glpi.WARNING: *** User Warning: Unexpected output detected in ./marketplace/ticketfilter/front/filterpattern.php. at LegacyFileLoadController.php line 94
Backtrace :
...Glpi/Controller/LegacyFileLoadController.php:94
./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\Controller\LegacyFileLoadController->__invoke()
./vendor/symfony/http-kernel/HttpKernel.php:76 Symfony\Component\HttpKernel\HttpKernel->handleRaw()
./vendor/symfony/http-kernel/Kernel.php:197 Symfony\Component\HttpKernel\HttpKernel->handle()
./public/index.php:70 Symfony\Component\HttpKernel\Kernel->handle()

Regards,

[alesnav]

Hi there!

Is this a blocking issue to use the new version of the plugin?

Thanks!

[DonutsNL]

Cause of the Issue
The legacy front files front/filterpattern.php and front/filterpattern.form.php include the core helper files /front/dropdown.common.php and /front/dropdown.common.form.php respectively. Under Symfony routing (using LegacyFileLoadController), these legacy entry points output/send the response directly, which closes the active output buffer started by Symfony and triggers the caught exceptions and warnings.

Modern GLPI 10+ Standard Solution
In modern GLPI 10+, physical front/*.php files are not required for subclasses of CommonDropdown or CommonDBTM. By deleting these legacy files, requests matching /plugins/ticketfilter/front/filterpattern.php (and .form.php) are intercepted by the core LegacyItemtypeRouteListener and dynamically routed to GenericListController and DropdownFormController.

We will also update FilterPattern::getMenuContent() to use the standard self::getSearchURL(false) instead of hardcoded paths.

It should not prevent you from using the plugin, its just not so nice. I will address this in a later version.