Bug 794411 (JBEPP-1455) - Docs: wrong description in user guide
Summary: Docs: wrong description in user guide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-1455
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0.Docs.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.Docs.GA
Assignee: Scott Mumford
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-12 12:42 UTC by vramik
Modified: 2014-06-17 13:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-13 06:36:26 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1455 0 None None None Never

Description vramik 2011-12-12 12:42:14 UTC
project_key: JBEPP

There are wrong descriptions of two methods in section 6.2.7. in User Guide.

My suggestion: Switch contents of these methods:

When you set skin using method one change is applied to this portal, and every user that accesses this portal will see it in the chosen skin.

When you change skin using method two, the skin is set for the logged in user and all portals within the domain will be shown with the chosen skin.

Method One
1. Click on Site, then Edit Portal's Properties.
2. In the Portal Setting tab, select another skin Skin list 
[...]

Method Two
1. Mouse over the Start menu and click on Change Skin. 
[...]

Another suggestion: 
Add "Skin changed by method two has higher priority." after "When you change skin using method two, the skin is set for the logged in user and all portals within the domain will be shown with the chosen skin."

Comment 1 Jared MORGAN 2011-12-12 22:35:31 UTC
Release Notes Docs Status: Added: Not Required


Comment 2 Scott Mumford 2011-12-13 06:36:26 UTC
Thanks for picking that up Vlastislav.

It's corrected in the latest version on stage (5.2.0-12)


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