May 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-376) Different Portlet preference for remote portlets added on the same page

by Anurag Debnath (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-376?page=com.atlassian.jira.plugi... ] Anurag Debnath updated GTNWSRP-376: ----------------------------------- Attachment: PortletPreferencesPortlet.war.zip One can use the attached portlet example to replicate the issue following the steps mentioned in the "Steps to Reproduce" section (Restricted to jira-users group) > Different Portlet preference for remote portlets added on the same page > ----------------------------------------------------------------------- > > Key: GTNWSRP-376 > URL: https://issues.jboss.org/browse/GTNWSRP-376 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.11.Final > Environment: Tested with : > JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5) and > GateIn-3.8.0.Beta01 > Reporter: Anurag Debnath > Assignee: Juraci Paixão Kröhling > Attachments: PortletPreferencesPortlet.war.zip > > > When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well. > Ideally, portlets should get their own preference/s. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-376) Different Portlet preference for remote portlets added on the same page

by Anurag Debnath (JIRA)

Anurag Debnath created GTNWSRP-376: -------------------------------------- Summary: Different Portlet preference for remote portlets added on the same page Key: GTNWSRP-376 URL: https://issues.jboss.org/browse/GTNWSRP-376 Project: GateIn WSRP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.11.Final Environment: Tested with : JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5) and GateIn-3.8.0.Beta01 Reporter: Anurag Debnath Assignee: Juraci Paixão Kröhling When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well. Ideally, portlets should get their own preference/s. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3458) Use infinite TTL for TemplateService caching by default

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3458?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3458: ---------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Trong Tran Resolution: Done > Use infinite TTL for TemplateService caching by default > ------------------------------------------------------- > > Key: GTNPORTAL-3458 > URL: https://issues.jboss.org/browse/GTNPORTAL-3458 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Trong Tran > Priority: Minor > Fix For: 3.9.0.Final > > > I think it makes sense to use infinite TTL for default TemplateService caching config as the number of templates are fixed and they never change in production ideally -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3458) Use infinite TTL for TemplateService caching by default

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3458?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3458: ---------------------------------- Fix Version/s: 3.9.0.Final (was: 3.8.0.Final) > Use infinite TTL for TemplateService caching by default > ------------------------------------------------------- > > Key: GTNPORTAL-3458 > URL: https://issues.jboss.org/browse/GTNPORTAL-3458 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Priority: Minor > Fix For: 3.9.0.Final > > > I think it makes sense to use infinite TTL for default TemplateService caching config as the number of templates are fixed and they never change in production ideally -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3471) impossible to edit a disable user

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3471?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3471: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.1.Final Resolution: Done > impossible to edit a disable user > --------------------------------- > > Key: GTNPORTAL-3471 > URL: https://issues.jboss.org/browse/GTNPORTAL-3471 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final, 3.8.0.Beta01 > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > Fix For: 3.7.1.Final, 3.8.1.Final > > > 1- Login as root > 2- Go to user management page > 3- Choose the tab "User Management" > -> A disabled user is displayed > 4- click on the button "Edit" > Actual Result: > A warning pop up is displayed "This user is disabled. You have to enable this user for editing. " > Expected Result: > User should be able to edit disabled user -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3471) impossible to edit a disable user

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3471?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-3471: ---------------------------------- Fix Version/s: 3.7.1.Final > impossible to edit a disable user > --------------------------------- > > Key: GTNPORTAL-3471 > URL: https://issues.jboss.org/browse/GTNPORTAL-3471 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final, 3.8.0.Beta01 > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > Fix For: 3.7.1.Final > > > 1- Login as root > 2- Go to user management page > 3- Choose the tab "User Management" > -> A disabled user is displayed > 4- click on the button "Edit" > Actual Result: > A warning pop up is displayed "This user is disabled. You have to enable this user for editing. " > Expected Result: > User should be able to edit disabled user -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3415) URL query parameters are lost in the authentication process with LegacyRequestHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3415?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3415: ---------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from ON_QA to VERIFIED > URL query parameters are lost in the authentication process with LegacyRequestHandler > ------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3415 > URL: https://issues.jboss.org/browse/GTNPORTAL-3415 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Martin Weiler > Assignee: Peter Palaga > Fix For: 3.8.0.Beta01 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Steps to reproduce > - Goto url http://localhost:8080/portal/private/classic/home/restricted?myparameter=... > --> it redirect to login page, login as root --> Query parameters are lost. > Note: Without the LegacyRequestHandler - http://localhost:8080/portal/classic/home/restricted?myparameter=TEST - the parameters are preserved with the fix for GTNPORTAL-3389 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3389) URL query parameters are not propagated when going through the authentication process

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3389?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3389: ---------------------------------------------------- Tomas Kyjovsky <tkyjovsk(a)redhat.com> changed the Status of [bug 1064421|https://bugzilla.redhat.com/show_bug.cgi?id=1064421] from ON_QA to VERIFIED > URL query parameters are not propagated when going through the authentication process > ------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3389 > URL: https://issues.jboss.org/browse/GTNPORTAL-3389 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.8.Final > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > Fix For: 3.5.9.Final, 3.7.0.Final > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Steps to reproduce > - Goto url http://localhost:8080/portal/g/:platform:administrators/administration/re... > --> it redirect to login page, login as root --> Query parameters are lost. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3471) impossible to edit a disable user

by Vu Viet Phuong (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3471?page=com.atlassian.jira.pl... ] Vu Viet Phuong updated GTNPORTAL-3471: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/851 > impossible to edit a disable user > --------------------------------- > > Key: GTNPORTAL-3471 > URL: https://issues.jboss.org/browse/GTNPORTAL-3471 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.7.0.Final, 3.8.0.Beta01 > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > > 1- Login as root > 2- Go to user management page > 3- Choose the tab "User Management" > -> A disabled user is displayed > 4- click on the button "Edit" > Actual Result: > A warning pop up is displayed "This user is disabled. You have to enable this user for editing. " > Expected Result: > User should be able to edit disabled user -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3471) impossible to edit a disable user

by Vu Viet Phuong (JIRA)

Vu Viet Phuong created GTNPORTAL-3471: ----------------------------------------- Summary: impossible to edit a disable user Key: GTNPORTAL-3471 URL: https://issues.jboss.org/browse/GTNPORTAL-3471 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.8.0.Beta01, 3.7.0.Final Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong 1- Login as root 2- Go to user management page 3- Choose the tab "User Management" -> A disabled user is displayed 4- click on the button "Edit" Actual Result: A warning pop up is displayed "This user is disabled. You have to enable this user for editing. " Expected Result: User should be able to edit disabled user -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues May 2014