SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
Anonymous | Login | 2021-01-15 15:23 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0003541 | Endian Firewall | Hotspot | public | 2011-03-16 17:37 | 2011-08-12 16:34 | ||||||
Reporter | lorenzo-endian | ||||||||||
Assigned To | simon-endian | ||||||||||
Priority | normal | Severity | feature | Reproducibility | have not tried | ||||||
Status | confirmed | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Product Version | |||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 0003541: Improve ASA interfacement | ||||||||||
Description | there is an option for ASA on which you select which ticket you want to be added to the user (you are not allowed to change the price of a ticket, because it would destroy all balances)so you have to rename the ticket and create a new ticket with the new price. In order to get it to use the ticket you have to select the new ticket on the ASA settings page. Moreover, another problem could arise, because old user for example have the old post paied ticket so the user has to manually expire those tickets in order to get their surftime accounted with the new ticket. The solution would be, man can change the price of a ticket, a new rate is created in the background and the old is linked to it for reference on old accounting entries. Simon has already discussed the weird behaviour together with ASA, that on every logon a ticket is added which should not be done but was allways done this way thats why we did not change it.... The feature request could be summerized as follows 1. make rate editable -> if the rate changes a new rate is added and the old rate is linked to it if a new ticket with that name is added allways the newest entry is used 2. with asa a ticket should only be added if the user is not able to surf anymore + if the postpayed ticket used is deprecated (rate price was changed) it should be expired and the new one should be added | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
||||||
|
![]() |
|||
Date Modified | Username | Field | Change |
2011-03-16 17:37 | lorenzo-endian | New Issue | |
2011-03-16 17:38 | lorenzo-endian | Assigned To | => simon-endian |
2011-03-16 17:38 | lorenzo-endian | Severity | minor => feature |
2011-03-16 17:38 | lorenzo-endian | Status | new => confirmed |
2011-08-12 17:07 | lorenzo-endian | Relationship added | parent of 0004114 |
Copyright © 2000 - 2012 MantisBT Group |