[JBoss JIRA] (GTNPORTAL-3235) Navigation nodes in navigation editor don't change label after portal language changed
by Son Tran (JIRA)
Son Tran created GTNPORTAL-3235:
-----------------------------------
Summary: Navigation nodes in navigation editor don't change label after portal language changed
Key: GTNPORTAL-3235
URL: https://issues.jboss.org/browse/GTNPORTAL-3235
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Son Tran
Assignee: Son Tran
Priority: Minor
- Login as "root" --> Try to edit navigation (Open navigation editor)
- Add node "test". Use "Extended Label Mode":
+ label for English : enLabel
+ label for French : frLabel
- Save all
- Open navigation editor again, now change language to French
---> Error : the test node's label doesn't change language to "frLabel"
The problem here is "resolvedLabel" is cached in UserNode, and it's only resolved one time
--
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, 4 months
[JBoss JIRA] (GTNPORTAL-3234) Add the conditional comments for IE
by Tuyen Nguyen The (JIRA)
Tuyen Nguyen The created GTNPORTAL-3234:
-------------------------------------------
Summary: Add the conditional comments for IE
Key: GTNPORTAL-3234
URL: https://issues.jboss.org/browse/GTNPORTAL-3234
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WebUI
Reporter: Tuyen Nguyen The
Assignee: Tuyen Nguyen The
We have some bugs only on IE (ie9, ie8).We should add Conditional comments to <html> tag
so UI team can fix bug on ie base on class "ie8" , ie9..
this is my suggestion
{code:xml}
<!--[if IE 7]> <html class="ie7 lt-ie8 lt-ie9 lt-ie10"> <![endif]-->
<!--[if IE 8]> <html class="ie8 lt-ie9 lt-ie10"> <![endif]-->
<!--[if IE 9]> <html class="ie9 lt-ie10"> <![endif]-->
<!--[if gt IE 9]> <html class=" ie10"> <![endif]-->
{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, 4 months
[JBoss JIRA] (GTNPORTAL-3182) Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3182:
---------------------------------------
Yes, I think the PR is ok to merge.
I just created another JIRA for maximized component in Portal layout GTNPORTAL-3233
> Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3182
> URL: https://issues.jboss.org/browse/GTNPORTAL-3182
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Final
> Environment: GateIn portal 3.5.0
> Reporter: Adam Kovari
> Attachments: 00905214-src.zip, case_00903245_using_code_for_case_00905214.ppt, portal_classic_2013-07-19_14-34-18.zip, portletstates-testcase.zip
>
>
> 1- During the action phase a portlet of the layout (producer) raises an event that contains both the target portlet reference (portlet ID) and the target window state desired.
> 2- The consumer portlets of the event (note: all portlet in the page may not consume the raised event but only a subset of them will) check if they are the target portlet of the event. In such a case they change the WindowState to the target state.
> 3- What we observe is that mechanism works if we have:
> - only one consumer on the page
> - the consumer is in the last position of the consumer portlets.
>
> Cases where we have multiple consumer on the page and where the target consumer is not the last in the event consumer list changes the WindowState accoding to command but the rendering of the portlet does not correspond to the correct state. Typically when we desire to maximize the portlet the actual WindowState of all portlets are OK (1 portlet is maximized and others are normal) but the render phase of all portlets are evaluated which is not the case when you perform a maximize using the WindowState button on the UI or when the portlet is in the position last from the portlets recieving the event.
--
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, 4 months
[JBoss JIRA] (GTNPORTAL-3182) Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
by Adam Kovari (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ]
Adam Kovari commented on GTNPORTAL-3182:
----------------------------------------
Hmm, so do you think PR 609 is now safe to merge? I guess UIPortal maximized component is somewhat unrelated to this JIRA anyway.
> Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3182
> URL: https://issues.jboss.org/browse/GTNPORTAL-3182
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Final
> Environment: GateIn portal 3.5.0
> Reporter: Adam Kovari
> Attachments: 00905214-src.zip, case_00903245_using_code_for_case_00905214.ppt, portal_classic_2013-07-19_14-34-18.zip, portletstates-testcase.zip
>
>
> 1- During the action phase a portlet of the layout (producer) raises an event that contains both the target portlet reference (portlet ID) and the target window state desired.
> 2- The consumer portlets of the event (note: all portlet in the page may not consume the raised event but only a subset of them will) check if they are the target portlet of the event. In such a case they change the WindowState to the target state.
> 3- What we observe is that mechanism works if we have:
> - only one consumer on the page
> - the consumer is in the last position of the consumer portlets.
>
> Cases where we have multiple consumer on the page and where the target consumer is not the last in the event consumer list changes the WindowState accoding to command but the rendering of the portlet does not correspond to the correct state. Typically when we desire to maximize the portlet the actual WindowState of all portlets are OK (1 portlet is maximized and others are normal) but the render phase of all portlets are evaluated which is not the case when you perform a maximize using the WindowState button on the UI or when the portlet is in the position last from the portlets recieving the event.
--
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, 5 months
[JBoss JIRA] (GTNPORTAL-3182) Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3182?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3182:
---------------------------------------
I mean a portlet in Portal layout can be maximized, just like in Page layout
> Portal 'overriding' maximization of a window in case multiple portlets on the page receive any event but only one of them changes the portlet window mode
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3182
> URL: https://issues.jboss.org/browse/GTNPORTAL-3182
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Final
> Environment: GateIn portal 3.5.0
> Reporter: Adam Kovari
> Attachments: 00905214-src.zip, case_00903245_using_code_for_case_00905214.ppt, portal_classic_2013-07-19_14-34-18.zip, portletstates-testcase.zip
>
>
> 1- During the action phase a portlet of the layout (producer) raises an event that contains both the target portlet reference (portlet ID) and the target window state desired.
> 2- The consumer portlets of the event (note: all portlet in the page may not consume the raised event but only a subset of them will) check if they are the target portlet of the event. In such a case they change the WindowState to the target state.
> 3- What we observe is that mechanism works if we have:
> - only one consumer on the page
> - the consumer is in the last position of the consumer portlets.
>
> Cases where we have multiple consumer on the page and where the target consumer is not the last in the event consumer list changes the WindowState accoding to command but the rendering of the portlet does not correspond to the correct state. Typically when we desire to maximize the portlet the actual WindowState of all portlets are OK (1 portlet is maximized and others are normal) but the render phase of all portlets are evaluated which is not the case when you perform a maximize using the WindowState button on the UI or when the portlet is in the position last from the portlets recieving the event.
--
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, 5 months