You are not logged in.

Announcement

 Téléchargez la dernière version stable de GLPI      -     Et vous, que pouvez vous faire pour le projet GLPI ? :  Contribuer
 Download last stable version of GLPI                      -     What can you do for GLPI ? :  Contribute

#1 2013-09-26 03:26:44

lufa20
Member
Registered: 2013-03-07
Posts: 17

Alert Reservation Expired Bug

When the alert expired reservation is sent out, it is delivered as the following:

Writer:##reservation.user##
Associated item:##reservation.itemtype## - ##reservation.item.name##

Start date: ##reservation.begin##
End date:##reservation.end##
Comments: ##reservation.comment##
--
ML
Automatically generated by GLPI 0.84.2

It appears that the actual notification template is sent, instead of the values. Other reservation notifications (New Reservation,Reservation Deleted) work OK based on this same template.

Any ideas?

Last edited by lufa20 (2013-09-26 03:33:07)

Offline

#2 2013-09-27 09:43:28

yllen
GLPI-DEV
From: Sillery (51)
Registered: 2008-01-14
Posts: 15,278

Re: Alert Reservation Expired Bug

All tag are not available for all event (look at "show list of available tags").

By ex: you can't use  ##reservation.user## for an alert expired
and you must put your tag between ##FOREACHitems## ##ENDFOREACHitems##


CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

Offline

#3 2013-09-30 16:48:23

lufa20
Member
Registered: 2013-03-07
Posts: 17

Re: Alert Reservation Expired Bug

Thank you, i will look around. PS. I have not modified anything, this came in set up out of the box like that.

Offline

Board footer

Powered by FluxBB