Hello,
we are getting server error 500 when we try to open the item after the full text search.
Looking into the log we find the following:
Error: Call to undefined method Doctrine\ORM\QueryBuilder::createNamedParameter() in /var/www/html/omeka-s/application/Module.php:747
We already tried to use “composer update” but still the problem persists.
Can anyone give us some hint?
Many thanks for your help!
Marco
Can you show the lines after that Error line, the numbered ones? That will help narrow down the problem.
Hello,
Thank you for your reply. I’m sorry for my late answer, we have a local installation of Omeka-S to manage our own Library catalogue.
Here the full stack of the error:
Error: Call to undefined method Doctrine\ORM\QueryBuilder::createNamedParameter() in /var/www/html/omeka-s/application/Module.php:747
Stack trace:
#0 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(318): Omeka\Module->searchFulltext()
#1 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(168): Laminas\EventManager\EventManager->triggerListeners()
#2 /var/www/html/omeka-s/modules/EasyAdmin/src/View/Helper/PreviousNextResourceTrait.php(216): Laminas\EventManager\EventManager->triggerEvent()
#3 /var/www/html/omeka-s/modules/EasyAdmin/src/View/Helper/PreviousNextResourceTrait.php(118): EasyAdmin\View\Helper\PreviousNext->prepareSearch()
#4 /var/www/html/omeka-s/modules/EasyAdmin/src/View/Helper/PreviousNext.php(60): EasyAdmin\View\Helper\PreviousNext->getPreviousAndNextResourceIds()
#5 /var/www/html/omeka-s/vendor/laminas/laminas-view/src/Renderer/PhpRenderer.php(467): EasyAdmin\View\Helper\PreviousNext->__invoke()
#6 /var/www/html/omeka-s/modules/EasyAdmin/Module.php(796): Laminas\View\Renderer\PhpRenderer->__call()
#7 /var/www/html/omeka-s/modules/EasyAdmin/Module.php(547): EasyAdmin\Module->handleViewLayoutResourceShow()
#8 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(318): EasyAdmin\Module->handleViewLayoutResource()
#9 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(168): Laminas\EventManager\EventManager->triggerListeners()
#10 /var/www/html/omeka-s/application/src/View/Helper/Trigger.php(60): Laminas\EventManager\EventManager->triggerEvent()
#11 /var/www/html/omeka-s/vendor/laminas/laminas-view/src/Renderer/PhpRenderer.php(467): Omeka\View\Helper\Trigger->__invoke()
#12 /var/www/html/omeka-s/application/view/layout/layout-admin.phtml(25): Laminas\View\Renderer\PhpRenderer->__call()
#13 /var/www/html/omeka-s/vendor/laminas/laminas-view/src/Renderer/PhpRenderer.php(585): include(‘…’)
#14 /var/www/html/omeka-s/vendor/laminas/laminas-view/src/View.php(202): Laminas\View\Renderer\PhpRenderer->render()
#15 /var/www/html/omeka-s/vendor/laminas/laminas-mvc/src/View/Http/DefaultRenderingStrategy.php(92): Laminas\View\View->render()
#16 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(318): Laminas\Mvc\View\Http\DefaultRenderingStrategy->render()
#17 /var/www/html/omeka-s/vendor/laminas/laminas-eventmanager/src/EventManager.php(168): Laminas\EventManager\EventManager->triggerListeners()
#18 /var/www/html/omeka-s/vendor/laminas/laminas-mvc/src/Application.php(354): Laminas\EventManager\EventManager->triggerEvent()
#19 /var/www/html/omeka-s/vendor/laminas/laminas-mvc/src/Application.php(335): Laminas\Mvc\Application->completeRequest()
#20 /var/www/html/omeka-s/index.php(26): Laminas\Mvc\Application->run()
#21 {main}
Thank you for your help.
Kind regards.
Thanks for sharing those details.
It looks like this is an incompatibility between Easy Admin and Omeka S 4.2.0. Easy Admin includes an option in the settings form to display ‘Buttons “Previous/Next”’ and it’s that feature that’s causing the problem. Unchecking that option should resolve the problem, I think.
The incompatibility here can be fixed either in Easy Admin or Omeka S itself. We’re looking at a change on our side to avoid this problem, which would get released in Omeka S 4.2.1. A future updated version of Easy Admin might also fix the problem from its side, but I don’t believe there’s a fix there currently.
Edit: I believe this is fixed on the Easy Admin side in an update to that module. (Though it seems like there may be a different issue with the same feature in the updated version.)