[JBoss JIRA] Created: (GTNPORTAL-2007) Wrong merged JS after undeploy JS module in JavascriptConfigService
by Khoi Nguyen (JIRA)
Wrong merged JS after undeploy JS module in JavascriptConfigService
-------------------------------------------------------------------
Key: GTNPORTAL-2007
URL: https://issues.jboss.org/browse/GTNPORTAL-2007
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Khoi Nguyen
Assignee: Khoi Nguyen
Fix For: 3.2.0-M02
1) After undeploy WebApp --> need to remove corresponding JS modules, and refresh merged JS, but JavascriptConfigService.getMergedJavascript() still return "old" string. And extended JS modules are not merged in refeshMergedJavascript method of the service, lastModified time should be reset also
2) After the first call to getMergedJavascript method. Can't deploy more "normal" JS modules or "extended" JS module
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-2004) UIPage is not cached properly in UIPortal
by Khoi Nguyen (JIRA)
UIPage is not cached properly in UIPortal
-----------------------------------------
Key: GTNPORTAL-2004
URL: https://issues.jboss.org/browse/GTNPORTAL-2004
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01
Reporter: Khoi Nguyen
Assignee: Khoi Nguyen
Priority: Minor
Fix For: 3.2.0-M02
Currently, to ensure performance, we cache UIPage in UIPortal, but in the code that put UIPage object to the cache :
org.exoplatform.portal.webui.page.UIPageBody.getUIPage() method --> uiPortal.setUIPage(page.getId(), uiPage);
but the page.getId() is always null . So the cache doesn't work, we should use pageReference as the key
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (GTNPORTAL-1974) Add Node button always create new node on the top level
by Minh Hoang TO (Updated) (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-1974?page=com.atlassian.jira.pl... ]
Minh Hoang TO updated GTNPORTAL-1974:
-------------------------------------
Labels: EPP_5.1.x_Triage portal-s60 synced worked (was: EPP_5.1.x_Triage portal-s60 worked)
> Add Node button always create new node on the top level
> -------------------------------------------------------
>
> Key: GTNPORTAL-1974
> URL: https://issues.jboss.org/browse/GTNPORTAL-1974
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Michal Vanco
> Assignee: kien nguyen
> Labels: EPP_5.1.x_Triage, portal-s60, synced, worked
> Fix For: 3.2.0-M02
>
> Original Estimate: 4 hours
> Time Spent: 3 hours
> Remaining Estimate: 1 hour
>
> Using Add Node button in Navigation Management (Site or Group) always create new node at the top level.
> When you have some subnode selected and Add Node button is used, node is created at the top level.
> Only way to create subnode is to use context menu otherwise node selection is ignored.
> Maybe it's wanted behavior, but IMO users would appreciate to create node on current selection.
> Or is there reason for this behavior?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months