This is a snapshot of Indico's old Trac site. Any information contained herein is most probably outdated. Access our new GitHub site here.

Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#368 closed defect (fixed)

EVO plugin: END_BEFORE_START not captured

Reported by: dmartinc Owned by: dmartinc
Priority: low Milestone: v0.97.0
Component: Video Services Version: 0.97.0
Keywords: collaboration evo synchronize Cc:

Description

This is an error message sent by the EVO server that occurs if we try to create / modify an EVO booking so that the end date is before the start.
It is not being captured because normally the error checks should not allow such a request to be sent to EVO.
However this can happen if a booking is synchronized to an event and a special case of date changes happen.
We should therefore capture it in order to avoid an exception mail and show a fail reason to the user. Right now the user is correctly notified that a synchronized move changed but does not know the reason.

Change History (3)

comment:1 Changed 6 years ago by dmartinc

  • Owner set to dmartinc
  • Status changed from new to accepted

comment:2 Changed 5 years ago by david.martin.clavo@…

  • Resolution set to fixed
  • Status changed from accepted to closed

commit 81563bc0bc212afd62acfaf51a7c7b490951c551
Author: David Martín Clavo <david.martin.clavo@…>
Date: Fri Apr 9 15:36:05 2010 +0200

[FIX] EVO: END_BEFORE_START captured


  • fixes #368
  • This error should normally never happen on booking creation / modification but can happen when the user changes event dates and a booking is synchronized to the event.
  • The event date change can occur and the user is notified that the EVO booking could not be moved but does not know the reason. Also an email was sent.
  • Changed to capture it so that the reason is properly displayed.
  • Added some INFO level log statements.

comment:3 Changed 5 years ago by David Martín Clavo <david.martin.clavo@…>

In [81563bc0bc212afd62acfaf51a7c7b490951c551]:

[FIX] EVO: END_BEFORE_START captured

  • fixes #368
  • This error should normally never happen on booking creation / modification but can happen when the user changes event dates and a booking is synchronized to the event.
  • The event date change can occur and the user is notified that the EVO booking could not be moved but does not know the reason. Also an email was sent.
  • Changed to capture it so that the reason is properly displayed.
  • Added some INFO level log statements.
Note: See TracTickets for help on using tickets.