You are not logged in.
Pages: 1
The mailing service is sending 5+ month old ticket notifications, so I wanted to wipe the queue in the database(table glpi_queuednotifications). Is that ok? Won't this generate any problems?
Last edited by JVGomes (2022-07-04 22:26:10)
Offline
Hello JVGomes,
As stated in the documentation, you can infer the table name based on the URL you are looking at.
https://glpi-developer-documentation.re … onventions
For "front/queuednotification.php", table name is "glpi_queuednotifications".
For "front/ticket.php", table name is "glpi_tickets".
For "front/user.php", table name is "glpi_users".
Etc...
++
Besoin d'un support professionnel pour GLPI ? Pensez à GLPI Network ! https://glpi-project.org/fr/tarifs/
Connaissez-vous l'offre Cloud maintenue et supportée par l'équipe qui édite GLPI ?
Vous pouvez tester gratuitement pendant 45 jours ! https://glpi-network.cloud (ou plus si besoin)
Offline
My bad, so is it ok to wipe in the database itself? I'm afraid it'll break something else.
Offline
Your are not oblige to wipe it, just set "is_deleted = 1" for all rows.
UPDATE glpi_queuednotifications SET is_deleted = 1;
After that, GLPI automatic action "queuednotificationclean" : will take care of wiping the table regularly (deleting rows is_deleted=1).
++
Besoin d'un support professionnel pour GLPI ? Pensez à GLPI Network ! https://glpi-project.org/fr/tarifs/
Connaissez-vous l'offre Cloud maintenue et supportée par l'équipe qui édite GLPI ?
Vous pouvez tester gratuitement pendant 45 jours ! https://glpi-network.cloud (ou plus si besoin)
Offline
Thank you, it worked! Appreciate it.
Offline
Pages: 1