PacketFence - BTS - PacketFence
View Issue Details
0001538PacketFencecorepublic2012-09-04 12:282012-10-29 12:37
fgaudreault 
fgaudreault 
lowminoralways
resolvedfixed 
3.5.0 
3.6.1devel 
cc5719ccb34980bb335bfb31d6b33d0a3050ccc0
0001538: Missing query for accounting violation
When using a non-supported time frame for the accounting violations, the code says we should look at the data since the beginning of time. However, that sub is missing.

- Should we remove the unsupported time values from the REGEXP to check the trigger format?
- Should we add the proper sub?
- Should we support all time format?
No tags attached.
Issue History
2012-09-04 12:28fgaudreaultNew Issue
2012-10-19 11:27fgaudreaultTarget Version => general
2012-10-26 16:07fgaudreaultTarget Versiongeneral => 3.6.1
2012-10-29 12:36fgaudreaultgit revision => cc5719ccb34980bb335bfb31d6b33d0a3050ccc0
2012-10-29 12:36fgaudreaultNote Added: 0003260
2012-10-29 12:36fgaudreaultStatusnew => resolved
2012-10-29 12:36fgaudreaultResolutionopen => fixed
2012-10-29 12:36fgaudreaultAssigned To => fgaudreault
2012-10-29 12:37fgaudreaultFixed in Version => devel

Notes
(0003260)
fgaudreault   
2012-10-29 12:36   
I decided to force the usage of the D(aily) W(eekly) M(onthly) Y(early) modifiers in the trigger format.

Fixed in devel.