Bug 469909

Summary: The Notification Methods page has the wrong url for the "(-) delete user" toolbar
Product: [Community] Spacewalk Reporter: Jesus M. Rodriguez <jesusr>
Component: WebUIAssignee: Justin Sherrill <jsherril>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://fjs-0-02.rhndev.redhat.com/network/users/details/contact_methods/index.pxt?uid=82
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-25 20:01:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 456552    
Attachments:
Description Flags
notification methods with wrong url and wrong number of links
none
correct links on user details none

Description Jesus M. Rodriguez 2008-11-04 18:02:51 UTC
Created attachment 322457 [details]
notification methods with wrong url and wrong number of links

Description of problem:
The Notification Methods page has the wrong url for the "(-) delete user"
toolbar.

Incorrect url is : /network/users/details/delete_confirm.pxt?uid=82

The correct url should be:
/rhn/users/DeleteUser.do?uid=82

Also needs deactivate user toolbar as well:
/rhn/users/DisableUser.do?uid=82

Version-Release number of selected component (if applicable):
0.3

How reproducible:


Steps to Reproduce:
1. create a user
2. click on Notification Methods
3. click on (-) delete user
4. observer 404 error
  
Actual results:
404 error

Expected results:
user is deleted. The correct url 

Additional info:
the User Details pages has the correct url.

Comment 1 Jesus M. Rodriguez 2008-11-04 18:05:54 UTC
Created attachment 322459 [details]
correct links on user details

Comment 2 Jesus M. Rodriguez 2008-11-25 20:01:07 UTC

*** This bug has been marked as a duplicate of bug 467715 ***