You are not logged in.
Hi all,
We have recently upgraded to GLPI 9.4.2 and I create a number of dashboards and utilities from the GLPI database. One of them was to do with followups and this is now failing as the table glpi_ticketfollowups doesn't seem to exist anymore!? I can see glpi_tickettasks but not followups?
Any help would be greatly appreciated
Regards
Offline
tables is now called :
glpi_itilfollowups
Trouver la panne avant de réparer...
GLPI10.0.10 (ubuntu 22.04 PHP8.1 Mariadb10.6 ) plugins : comportements 2.7.2 reports 1.16.0 formcreator 2.13.8, datainjection 2.13.4 fields 1.21.6
Offline
Awesome! Thank you so much
Offline
thanks it works
Offline
tables is now called :
glpi_itilfollowups
Hello. Should I make any manual modification or apply a patch to correct the problem? I have the sql-errors.log that grows eternally with a bunch of errors to the fact that the glpi_ticketfollowups doesn't seem to exist anymore.
I'm running GLPI 9.4.3
Thanks.
Offline
LaDenrée wrote:tables is now called :
glpi_itilfollowupsHello. Should I make any manual modification or apply a patch to correct the problem? I have the sql-errors.log that grows eternally with a bunch of errors to the fact that the glpi_ticketfollowups doesn't seem to exist anymore.
I'm running GLPI 9.4.3
Thanks.
I answer myself, which I don't know if it is a valid solution. I saw somewhere in this forum that maybe the problem was due to the fact of an error during the upgrade. I don't remember seeing anything.
What I did to start off is to create a view with the old table name and the ID field that should be called tickets_id. Here is the SQL that I run on MySQL
CREATE VIEW glpi_ticketfollowups_test AS
SELECT *, id as tickets_id FROM glpi_itilfollowups;
Offline
Hello, got the same error after upgrading to 9.4.3, appear when adding or editing a followup on any opened ticket.
glpisqllog.ERROR: DBmysql::query() in /var/www/glpi/inc/dbmysql.class.php line 188
*** MySQL query error:
SQL: SELECT DISTINCT `glpi_users`.`id` AS `users_id`, `glpi_users`.`language` AS `language` FROM `glpi_ticketfollowups` INNER JOIN `glpi_users` ON (`glpi_ticketfollowups`.`users_id` = `glpi_users`.`id`) INNER JOIN `glpi_profiles_users` ON (`glpi_profiles_users`.`users_id` = `glpi_users`.`id`) WHERE (`glpi_profiles_users`.`entities_id` = '26' OR (`glpi_profiles_users`.`is_recursive` = '1' AND `glpi_profiles_users`.`entities_id` IN ('0'))) AND `glpi_ticketfollowups`.`id` = '34567'
Error: Table 'glpi.glpi_ticketfollowups' doesn't exist
Backtrace :
inc/dbmysqliterator.class.php:95
inc/dbmysql.class.php:580 DBmysqlIterator->execute()
...otificationtargetcommonitilobject.class.php:483 DBmysql->request()
...otificationtargetcommonitilobject.class.php:840 NotificationTargetCommonITILObject->addFollowupAuthor()
inc/notificationtarget.class.php:1123 NotificationTargetCommonITILObject->addSpecificTargets()
inc/notificationeventabstract.class.php:91 NotificationTarget->addForTarget()
inc/notificationevent.class.php:163 NotificationEventAbstract::raise()
inc/itilfollowup.class.php:275 NotificationEvent::raiseEvent()
inc/commondbtm.class.php:1142 ITILFollowup->post_addItem()
front/itilfollowup.form.php:49 CommonDBTM->add()
{"user":"493@vslglpi1pr031","mem_usage":"0.013\", 3.92Mio)"}
Seems the files /var/www/glpi/inc/dbmysql.class.php call the wrong table (the files was logically updated with the package glpi 9.4.2 and the edit/build date of the files is 20 june 2019 @15h06
Should I manually edit this files ?
Offline
also there were no errors during migration.
Offline
Hello, got the same error after upgrading to 9.4.3, appear when adding or editing a followup on any opened ticket.
Should I manually edit this files ?
I solved the problem like I mentioned in my post.
Offline
after taking wiht my dba, we applied the same solution as pepeimpulso by adding a view :
CREATE VIEW glpi_ticketfollowups as select * from glpi_itilfollowups;
=> Seems to work correctly, no more errors in sql-errors.log when adding or editing followups.
Maybe there a fix on github but not being a developers i really don't understand how to find something on it.
Offline