All work

Select view

Select search mode

 
50 of 51

Returns directory of "opennms/admin/notification/" when required fields are not provided for notification destination paths.

Fixed

Description

Problem:
"opennms/admin/notification/" directory structure is returned when you provide try to finish the notification destination path without providing all required fields.

noting the required fields and just popping an error and then sending the user back to the page with the info already populated if much friendlier. Checking the form might be able to be done with javascript so you don't actually have to post/get/process the value in the fields.

How to repeat:
Admin->Configure Notification->Configure Destination Paths->New Path
Name: Notify_Dest_Path_1
Click Finish

Returns you to a directory output of "opennms/admin/notification/" after giving a popup window saying you must fill out intial targets or whatever the required field is.

Environment

Version: 1.8.4 Server Time: Mon May 02 17:05:53 MST 2011 Client Time: Mon May 02 2011 17:05:53 GMT-0700 (US Mountain Standard Time) Java Version: 1.5.0_18 Sun Microsystems Inc. Java Virtual Machine: 1.5.0_18-b02 Sun Microsystems Inc. Operating System: Linux 2.6.18-164.el5PAE (i386) Servlet Container: jetty/6.1.24 (Servlet Spec 2.5) User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24

Acceptance / Success Criteria

None

Lucidchart Diagrams

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 2, 2011 at 8:19 PM
Updated June 23, 2011 at 3:22 PM
Resolved June 22, 2011 at 11:46 PM

Activity

Lance VermilionJune 23, 2011 at 3:22 PM

Alejandro has mentioned a version of 1.8.5 + will resolve the issue. I still need to verify this, but for now no need to keep this issue open when it has been verified in new version that it does not exist.

Lance VermilionJune 23, 2011 at 3:21 PM

I will look at upgrading in the future. Right now that is not really possible. I will try to find test VM and install a new version of ONMS and see if that resolves the issues as you have mentioned it should. Thx.

Alejandro GalueJune 22, 2011 at 11:46 PM

I tried to reproduce the problem on 1.8.11 and above and it works for me as expected. Try upgrading your OpenNMS.

Checking the code, the problem seems to be fixed on revision 8ced5a3bd46c39e3e4446ffb720ed002f9bb035f. So that means any version about 1.8.5 should work.