[JBoss JIRA] (GTNPORTAL-3044) Inconsistency in html elements of shared layout/user bar portlets
by Tuyen Nguyen The (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3044?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-3044 started by Tuyen Nguyen The.
> Inconsistency in html elements of shared layout/user bar portlets
> -----------------------------------------------------------------
>
> Key: GTNPORTAL-3044
> URL: https://issues.jboss.org/browse/GTNPORTAL-3044
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta02
> Environment: jboss-jpp-6.1.0.ER1-prod-17052013.zip
> Reporter: Vlastislav Ramik
> Assignee: Tuyen Nguyen The
> Labels: JPP61-Test-dev
> Original Estimate: 6 hours
> Time Spent: 3 hours
> Remaining Estimate: 3 hours
>
> Shared layout/user bar portlets (ie the bar that appears at the top of the page when you are a logged-in user) has following inconsistency:
> Portal Actions (that with the redhat icon): {noformat}<li title="Portal Actions" style="width: 62px" class="UITab portlet-menu-item">{noformat} The is also empty link as a child of the <li> but it has zero length.
> Site: {noformat}<a title="Sites" class="SitesIcon TBIcon" href="javascript:;">Site</a>{noformat}
> Group: {noformat}<span title="Group" class="GroupIcon TBIcon">Group</span>{noformat}
> Dashboard: If the user does not have any dashboard pages there is a link. If the user has a dashboard page there is a span. This is correct in my opinion.
> Site/Group/Dashboard Editor: {noformat}<a title="Site/Group/Dashboard Editor" href="#" class="EditorIcon TBIcon">Site/Group/Dashboard Editor</a>{noformat}
> All this leads to different looking cursors when you hovering the portlet.
> Portal Actions: arrow cursor
> Site: link cursor and text is highlighted
> Group:
> - arrow cursor when you are hovering that "people" icon
> - text cursor when you are hovering Group text
> Dashboard:
> - in case of none dashboard pages - it behaves the same as Site
> - in case on any dashboard pages - it behaves the same as Group
> Site/Group/Dashboard Editor: link cursor and text is highlighted
> The solution can be using css cursor (e.g. cursor: pointer; ) but cleaner solution would be probably unify it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-2703) There's "Access Permission" tab of Portlet edit window in Dashboard edit mode. How does it behave?
by Hai Nguyen (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2703?page=com.atlassian.jira.pl... ]
Hai Nguyen commented on GTNPORTAL-2703:
---------------------------------------
In the case of Dashboard page, nobody can access page without owner. But "Make it public (everyone can access)" of portlet setting uses to make it be accessed by everyone who can access the page contains it.
> There's "Access Permission" tab of Portlet edit window in Dashboard edit mode. How does it behave?
> --------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2703
> URL: https://issues.jboss.org/browse/GTNPORTAL-2703
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Beta01
> Reporter: Takayuki Konishi
> Assignee: Hai Nguyen
> Attachments: AccessPermissionTab.png
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> What is the function of "Access Permission" tab of Portlet edit window in Dashboard edit mode; especially the case of the login user has not admin permission.
> How does "Make it public (everyone can access):" checkbox behave?
> If it have no function, please delete it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-2703) There's "Access Permission" tab of Portlet edit window in Dashboard edit mode. How does it behave?
by Hai Nguyen (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2703?focusedWorklogId=12429777&... ]
Hai Nguyen logged work on GTNPORTAL-2703:
-----------------------------------------
Author: Hai Nguyen
Created on: 22/Sep/13 11:29 PM
Start Date: 22/Sep/13 11:29 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour (was: 2 hours)
Time Spent: 1 hour
Worklog Id: (was: 12429777)
> There's "Access Permission" tab of Portlet edit window in Dashboard edit mode. How does it behave?
> --------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2703
> URL: https://issues.jboss.org/browse/GTNPORTAL-2703
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Beta01
> Reporter: Takayuki Konishi
> Assignee: Hai Nguyen
> Attachments: AccessPermissionTab.png
>
> Original Estimate: 2 hours
> Time Spent: 1 hour
> Remaining Estimate: 1 hour
>
> What is the function of "Access Permission" tab of Portlet edit window in Dashboard edit mode; especially the case of the login user has not admin permission.
> How does "Make it public (everyone can access):" checkbox behave?
> If it have no function, please delete it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-2713) GateIn doesn't work after reloading AS7
by Hai Nguyen (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2713?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-2713 started by Hai Nguyen.
> GateIn doesn't work after reloading AS7
> ---------------------------------------
>
> Key: GTNPORTAL-2713
> URL: https://issues.jboss.org/browse/GTNPORTAL-2713
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Hai Nguyen
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> GateIn doesn't work after AS7 has been reloaded (using the management interface).
> Stack trace:
> {code}
> 14:25:48,980 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."gatein.ear".gatein.init: org.jboss.msc.service.StartException in service jboss.deployment.unit."gatein.ear".gatein.init: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> Caused by: org.picocontainer.defaults.DuplicateComponentKeyRegistrationException: Key class org.gatein.integration.wsrp.plugins.AS7Plugins duplicated
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponent(ConcurrentPicoContainer.java:237)
> at org.exoplatform.container.mc.MCIntegrationContainer.registerComponent(MCIntegrationContainer.java:108)
> at org.exoplatform.container.CachingContainer.registerComponent(CachingContainer.java:174)
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponentInstance(ConcurrentPicoContainer.java:292)
> at org.exoplatform.container.CachingContainer.registerComponentInstance(CachingContainer.java:196)
> at org.exoplatform.container.management.ManageableContainer.registerComponentInstance(ManageableContainer.java:220)
> at org.gatein.integration.jboss.as7.web.InitService.start(InitService.java:66)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GTNPORTAL-2713) GateIn doesn't work after reloading AS7
by Hai Nguyen (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2713?page=com.atlassian.jira.pl... ]
Hai Nguyen reassigned GTNPORTAL-2713:
-------------------------------------
Assignee: Hai Nguyen
> GateIn doesn't work after reloading AS7
> ---------------------------------------
>
> Key: GTNPORTAL-2713
> URL: https://issues.jboss.org/browse/GTNPORTAL-2713
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Hai Nguyen
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> GateIn doesn't work after AS7 has been reloaded (using the management interface).
> Stack trace:
> {code}
> 14:25:48,980 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."gatein.ear".gatein.init: org.jboss.msc.service.StartException in service jboss.deployment.unit."gatein.ear".gatein.init: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> Caused by: org.picocontainer.defaults.DuplicateComponentKeyRegistrationException: Key class org.gatein.integration.wsrp.plugins.AS7Plugins duplicated
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponent(ConcurrentPicoContainer.java:237)
> at org.exoplatform.container.mc.MCIntegrationContainer.registerComponent(MCIntegrationContainer.java:108)
> at org.exoplatform.container.CachingContainer.registerComponent(CachingContainer.java:174)
> at org.exoplatform.container.ConcurrentPicoContainer.registerComponentInstance(ConcurrentPicoContainer.java:292)
> at org.exoplatform.container.CachingContainer.registerComponentInstance(CachingContainer.java:196)
> at org.exoplatform.container.management.ManageableContainer.registerComponentInstance(ManageableContainer.java:220)
> at org.gatein.integration.jboss.as7.web.InitService.start(InitService.java:66)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months