Bug 850703 - 'Read Right' checkbox is not behaving as expected
Summary: 'Read Right' checkbox is not behaving as expected
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Site Publisher
Version: 5.2.1.SP.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-22 07:43 UTC by bkramer
Modified: 2025-02-10 03:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description bkramer 2012-08-22 07:43:37 UTC
Description of problem:
Under Permissions Tab,
Edit any user permissions, uncheck 'Read Right' checkbox and click on save button
'Read Right' option is still appearing as 'true'.

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

How reproducible:
Always

Steps to Reproduce:
1) Log into Site Publisher as root;
2) From the menu navigate to Group -> Administration -> Manage Categories;
3) From the list of Categories -> acme -> in the Action select "Edit Category Tree";
4) Click on "+" to list categories;
5) From the right table -> for one category name -> select "Permission Management" icon;
6) Select user by clicking on pencil icon in Action column. This will display selected user in the "Add permission to that node" section with all permissions.
7) Remove "Read" right by unselecting "Read" check box and click on "Save" button to save the change;
8) Select the same user again and check it's permissions and it will show again "Read" as enabled.

  
Actual results:
The checkbox appears as "checked".

Expected results:
It should appear as 'False' after uncheck the checkbox.

Additional info:

Comment 2 Red Hat Bugzilla 2025-02-10 03:20:32 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.