Form check for illegal characters (1)
Posted: Mon Jan 03, 2011 10:47 pm
Using Core Configuration Manager, the form check is not always used in certain areas.
For example when I duplicate a host and then mark it active I am not allowed to save the object as it has the illegal characters in the hostname (1) and is pops up a window telling me. This is the expected behaviour.
However for the following areas of Core Configuation Manager this check is not performed and of course causes issues when applying configuration.
Host Groups
Service Groups
Contacts
Contact Groups
Time Periods
Commands
The following areas do not have any problem saving objects with (1) in the name (apply configuration works fine), I am unsure if this is by design.
Host Escalation
Service Escalation
Host Templates
Service Templates
Contact Templates
This occurs on Nagios XI 2009R1.3G, VMware image running on ESXi.
Just thought you would like to know.
For example when I duplicate a host and then mark it active I am not allowed to save the object as it has the illegal characters in the hostname (1) and is pops up a window telling me. This is the expected behaviour.
However for the following areas of Core Configuation Manager this check is not performed and of course causes issues when applying configuration.
Host Groups
Service Groups
Contacts
Contact Groups
Time Periods
Commands
The following areas do not have any problem saving objects with (1) in the name (apply configuration works fine), I am unsure if this is by design.
Host Escalation
Service Escalation
Host Templates
Service Templates
Contact Templates
This occurs on Nagios XI 2009R1.3G, VMware image running on ESXi.
Just thought you would like to know.