glpi-project/glpi

Error when trying to load the list of created ticket templates GLPI 11 Rc5

Closed this issue · 1 comments

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

Version

GLPI 11 RC5

Bug description

When trying to associate a call model within the profile > assistance, this message appears: the results could not be loaded.

Image

Whenever I click on this button to try to associate a model with the profile, it gives this error in the log:

glpi.CRITICAL: *** Uncaught PHP Exception RuntimeException: "MySQL query error: Unknown column 'glpi_tickettemplates.entity' in 'WHERE' (1054) in SQL query "SELECT DISTINCT glpi_tickettemplates.* FROM glpi_tickettemplates WHERE glpi_tickettemplates.entity = '0' AND glpi_tickettemplates.is_recursive = '1' AND (true) ORDER BY glpi_tickettemplates.entities_id, glpi_tickettemplates.name LIMIT 100"." at DBmysql.php line 381
Backtrace :
./src/DBmysql.php:381
./src/DBmysqlIterator.php:123 DBmysql->doQuery()
./src/DBmysql.php:1050 DBmysqlIterator->execute()
./src/Dropdown.php:3599 DBmysql->request()
./ajax/getDropdownValue.php:48 Dropdown::getDropdownValue()
...Glpi/Controller/LegacyFileLoadController.php:63 require()
./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()

The strange thing is that if I go to administration > entities > root entity > assistance > templates, I can see the list of templates created.

I tried clearing the cache, logging out and back in, etc., but without success.

Relevant log output

Page URL

No response

Steps To reproduce

No response

Your GLPI setup information

No response

Anything else?

No response

To add to that: although I have this criticism in the profile, if I leave the default model associated with the entity, I can see the changes to the model within the call normally. It seems that it is only in the profile that it is not okay to try to associate a model other than the entity's default or even view the list of models created.