PacketFence - BTS - PacketFence
View Issue Details
0001361PacketFenceweb adminpublic2012-01-10 11:122012-02-28 14:31
obilodeau 
obilodeau 
normalminoralways
closedfixed 
 
3.2.03.2.0 
377963591ecec0fca3d69c17e54aa0c51b3257ea
0001361: Emptying a configuration parameter doesn't work from web admin and pfcmd
For example:

Trying to get rid of guest self registration from the web admin results in:

Unable to change guests_self_registration_modes from 'sms,email' to ''

Trying from the command line (pfcmd config set ...) also fails. Actually the problem resides there.
No tags attached.
Issue History
2012-01-10 11:12obilodeauNew Issue
2012-01-10 11:12obilodeauStatusnew => assigned
2012-01-10 11:12obilodeauAssigned To => obilodeau
2012-01-29 13:42obilodeauNote Added: 0002558
2012-02-01 14:45obilodeauNote Added: 0002564
2012-02-01 15:45obilodeauNote Added: 0002565
2012-02-03 16:37obilodeauNote Added: 0002567
2012-02-03 16:37obilodeauStatusassigned => resolved
2012-02-03 16:37obilodeauFixed in Version => trunk
2012-02-03 16:37obilodeauResolutionopen => fixed
2012-02-03 16:38obilodeaumtn revision => 377963591ecec0fca3d69c17e54aa0c51b3257ea
2012-02-28 14:22obilodeauTarget Version+1 => 3.2.0
2012-02-28 14:22obilodeauFixed in Versiontrunk => 3.2.0
2012-02-28 14:31obilodeauNote Added: 0002588
2012-02-28 14:31obilodeauStatusresolved => closed

Notes
(0002558)
obilodeau   
2012-01-29 13:42   
I have a regression test ready. The problem is in the parameter parser (grammar). Not sure how I'll fix it yet.
(0002564)
obilodeau   
2012-02-01 14:45   
Turns out that making pfcmd accept empty values was easy but now in the interface there's a problem: it can't differentiate an empty value from a default value.
(0002565)
obilodeau   
2012-02-01 15:45   
I am adding a enable/disable flag under [registration] instead. It makes a lot more sense to go that way.
(0002567)
obilodeau   
2012-02-03 16:37   
enabled / disabled flag created that controls self guest registration. No need to set to "" now.
(0002588)
obilodeau   
2012-02-28 14:31   
Fixed in recently released 3.2.0.