[JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3417:
----------------------------------------------------
Lucas Ponce <lponce(a)redhat.com> changed the Status of [bug 1076175|https://bugzilla.redhat.com/show_bug.cgi?id=1076175] from ASSIGNED to POST
> Disable users icons look like inverse
> -------------------------------------
>
> Key: GTNPORTAL-3417
> URL: https://issues.jboss.org/browse/GTNPORTAL-3417
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: 3.8.0.Beta01-SNAPSHOT
> Reporter: Vlastislav Ramik
> Assignee: Lucas Ponce
> Labels: RHJP62
> Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3464) Enabled/disabled users icons
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3464?page=com.atlassian.jira.pl... ]
Lucas Ponce updated GTNPORTAL-3464:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/848
> Enabled/disabled users icons
> ----------------------------
>
> Key: GTNPORTAL-3464
> URL: https://issues.jboss.org/browse/GTNPORTAL-3464
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.8.0.Beta01
> Reporter: Lucas Ponce
> Assignee: Lucas Ponce
> Fix For: 3.8.0.Final
>
>
> Enabled users have a grey icon and disable users have a green icon in users admin app.
> This create some confusion at UI as expected behaviour colors are the opposity.
> A good solution for that would be to update the column title
> “Enabled” to “Status”. Also, with this kind of label, the icon must indicate
> the current status. So, grey icon for disabled and green icon for enabled.
> The tooltip also must indicate the current status, so it should say
> “Disabled User” for gray icons and “Enabled User” for green icons.
>
> When the user clicks on the icon, it should change for the opposite, and the text in the tooltip should be updated.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.pl... ]
Lucas Ponce reassigned GTNPORTAL-3417:
--------------------------------------
Assignee: Lucas Ponce
> Disable users icons look like inverse
> -------------------------------------
>
> Key: GTNPORTAL-3417
> URL: https://issues.jboss.org/browse/GTNPORTAL-3417
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: 3.8.0.Beta01-SNAPSHOT
> Reporter: Vlastislav Ramik
> Assignee: Lucas Ponce
> Labels: RHJP62
> Fix For: 3.8.0.Final
>
>
> Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3464) Enabled/disabled users icons
by Lucas Ponce (JIRA)
Lucas Ponce created GTNPORTAL-3464:
--------------------------------------
Summary: Enabled/disabled users icons
Key: GTNPORTAL-3464
URL: https://issues.jboss.org/browse/GTNPORTAL-3464
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 3.8.0.Beta01
Reporter: Lucas Ponce
Assignee: Lucas Ponce
Fix For: 3.8.0.Final
Enabled users have a grey icon and disable users have a green icon in users admin app.
This create some confusion at UI as expected behaviour colors are the opposity.
A good solution for that would be to update the column title
“Enabled” to “Status”. Also, with this kind of label, the icon must indicate
the current status. So, grey icon for disabled and green icon for enabled.
The tooltip also must indicate the current status, so it should say
“Disabled User” for gray icons and “Enabled User” for green icons.
When the user clicks on the icon, it should change for the opposite, and the text in the tooltip should be updated.
--
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
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3435) Import .zip REST API broken with EAP 6.3.0.Alpha1
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3435?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3435:
----------------------------------------------------
Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1083054|https://bugzilla.redhat.com/show_bug.cgi?id=1083054] from ON_QA to VERIFIED
> Import .zip REST API broken with EAP 6.3.0.Alpha1
> -------------------------------------------------
>
> Key: GTNPORTAL-3435
> URL: https://issues.jboss.org/browse/GTNPORTAL-3435
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Lucas Ponce
> Assignee: Lucas Ponce
> Attachments: jbossweb-7.4.1.Final.jar, portal_classic_2014-03-28_16-59-29.zip
>
>
> A curl operation over template/user API:
> curl -i -H "Content-Type: application/zip" -u root:gtn -X PUT -T examples/user.zip "http://localhost:8080/rest/private/managed-components/template/user"
> hangs with:
> 16:35:16,466 INFO [org.exoplatform.portal.mop.management.operations.TemplateImportResource] (http-/127.0.0.1:8080-4) Import successful !
> 16:35:16,475 ERROR [org.apache.catalina.connector] (http-/127.0.0.1:8080-4) JBWEB001018: An exception or error occurred in the container during the request processing: java.nio.BufferOverflowException
> at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:357) [rt.jar:1.7.0_25]
> at org.apache.coyote.http11.InternalNioOutputBuffer.commit(InternalNioOutputBuffer.java:666) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.http11.Http11NioProcessor.commit(Http11NioProcessor.java:480) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.http11.Http11NioProcessor.action(Http11NioProcessor.java:798) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.Response.action(Response.java:190) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.Response.sendHeaders(Response.java:390) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:352) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:318) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.catalina.connector.Response.finishResponse(Response.java:487) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:371) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:353) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:911) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:920) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
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
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3463) Update GateIn to WSRP 2.3.1.Final
by Juraci Paixão Kröhling (JIRA)
Juraci Paixão Kröhling created GTNPORTAL-3463:
-------------------------------------------------
Summary: Update GateIn to WSRP 2.3.1.Final
Key: GTNPORTAL-3463
URL: https://issues.jboss.org/browse/GTNPORTAL-3463
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Juraci Paixão Kröhling
Assignee: Juraci Paixão Kröhling
A new release for WSRP was made, thus requiring a change in GateIn Portal to consume this new version.
--
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
10 years, 8 months
[JBoss JIRA] (GTNPORTAL-3263) "Restricted" page editor
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3263?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3263:
----------------------------------------------------
vramik(a)redhat.com changed the Status of [bug 1038562|https://bugzilla.redhat.com/show_bug.cgi?id=1038562] from ON_QA to VERIFIED
> "Restricted" page editor
> ------------------------
>
> Key: GTNPORTAL-3263
> URL: https://issues.jboss.org/browse/GTNPORTAL-3263
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> See https://community.jboss.org/wiki/RestrictedPageEditor
> A customer is willing to give the ability to many different users to edit pages. Those users would require a simplified page editor and be constrained to simple actions. In particular, users should not be able to compose complex pages and risk to break the layouts.
> The layouts should be restricted to what is available from the "Containers" tab of the editor.
> In particular the 2 following scenarios should not be possible:
> Scenario 1: User should not be able to put an application above/below the 2 column layout (As this break the pre-defined layouts, suddenly the user is able to have a single column representation while this may not have been provided):
> Scenario 2: User should not be able to put a layout within a layout (only above or below existing ones)
> Proposed solution
> Add an option in configuration.properties for a restricted page and layout editor. This would apply across the whole portal.
> gatein.portal.pageeditor.mode=full (default) | restricted
> gatein.portal.layouteditor.mode=full (default) | restricted
>
> Applications could only be added to predefined layouts (and not directly on a page).
> Containers could only be added to the root of a page (not inside another container).
--
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
10 years, 8 months