| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001823 | PacketFence | web admin | public | 2014-09-05 10:22 | 2014-09-05 10:22 |
|
| Reporter | jsemaan.inverse | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | All | OS | All | OS Version | All |
| Product Version | devel | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001823: The external script trigger for violations is broken in the admin ui |
| Description | The creation of external script triggers in the admin ui creates invalid configuration.
It adds the trigger 'external' when the configuration expects
'external<some user defined id>'
Then the path to the script must be configured in pf.conf in
[paths.external<the decided id>]
It must also be added to documentation.conf or pf won't checkup.
We need to review the way we create these triggers or adapt the admin interface to the current way of doing it.
The feature still works when creating the configuration manually |
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Relationships 