0001351: i can't change email_activation_timeout - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001351

PacketFence

configuration

public

2011-12-22 07:32

2011-12-22 09:09

Reporter

samehsamir

Assigned To

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

3.0.1

Target Version

Fixed in Version

3.0.2

Summary

0001351: i can't change email_activation_timeout

Description

The guest self-registration commands are not recognized as a valid commands when I added them.the release we have is 3.0.1

[guests_self_registration]
modes=sms,email
category=guest
access_duration=7d
email_activation_timeout=10m
allow_localdomain=enabled

[root@pf-zen ~]# /etc/init.d/packetfence restart
Restarting PacketFence...service|command
dhcpd|stop
httpd|stop
pfdhcplistener|stop
pfmon|stop
Checking configuration sanity...
FATAL - unknown configuration parameter guests_self_registration.modes if you added the parameter yourself make sure it is present in conf/documentation.conf
FATAL - unknown configuration parameter guests_self_registration.category if you added the parameter yourself make sure it is present in conf/documentation.conf
FATAL - unknown configuration parameter guests_self_registration.access_duration if you added the parameter yourself make sure it is present in conf/documentation.conf
FATAL - unknown configuration parameter guests_self_registration.email_activation_timeout if you added the parameter yourself make sure it is present in conf/documentation.conf
FATAL - unknown configuration parameter guests_self_registration.allow_localdomain if you added the parameter yourself make sure it is present in conf/documentation.conf

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0002481) dwuelfrath (administrator) 2011-12-22 09:06	Those new config flags were added in the PacketFence 3.0.2 release. This is the reason why you're getting these errors while trying to use them in version 3.0.1. Release note: http://www.packetfence.org/news/2011/article/packetfence-302-released.html [^] See enhancement number 3. Related to this revision: http://mtn.inverse.ca/revision/info/23879b32a8f945de1da96869ab569db961c8b09d [^]

(0002482) dwuelfrath (administrator) 2011-12-22 09:09	I've also updated the product version of your ticket to 3.0.1 instead of 3.0.3 according your ticket description.

Issue History
Date Modified	Username	Field	Change
2011-12-22 07:32	samehsamir	New Issue
2011-12-22 09:06	dwuelfrath	Note Added: 0002481
2011-12-22 09:09	dwuelfrath	Note Added: 0002482
2011-12-22 09:09	dwuelfrath	Status	new => closed
2011-12-22 09:09	dwuelfrath	Resolution	open => fixed
2011-12-22 09:09	dwuelfrath	Product Version	3.0.3 => 3.0.1
2011-12-22 09:09	dwuelfrath	Fixed in Version	=> 3.0.2