[JBoss JIRA] Created: (GTNPORTAL-975) Date format bug in PublishDate during Node creation
by Arthur Peltier (JIRA)
Date format bug in PublishDate during Node creation
---------------------------------------------------
Key: GTNPORTAL-975
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-975
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: ff, xp, tomcat, 1.6, n/a
Reporter: Arthur Peltier
Priority: Minor
Portal\Portal Navigation\Node\Create
*Login as root
*go to site link and edit Navigation
*Add node with "Publication date & time"
*fill date and save input in format "dd/mm/yy hh:mm:ss" is possible but after save it becomes "dd/mm/00yy hh:mm:ss". I should at least put ".../20yy hh:..." by default.
Result : "03/09/0011 14:27:55" I doubt it will ever be published
Expected : having put in "03/09/11 14:27:55" during creation I wanted "03/09/2011 14:27:55"
linked to test POR_14_01_026
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1284) Optimize SiteMap portlet by setting a filter on the node tree instead of using PageNavigationUtils.filter
by Minh Hoang TO (JIRA)
Optimize SiteMap portlet by setting a filter on the node tree instead of using PageNavigationUtils.filter
---------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1284
URL: https://jira.jboss.org/browse/GTNPORTAL-1284
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Minh Hoang TO
Assignee: Minh Hoang TO
In current code of SiteMap portlet, whenever there is a call to reload the tree (on expand/collapse the node), the filter method in PageNavigationsUtils is implicitely invoked. That results in two drawbacks:
1. A traverse over navigation trees is required, whereas on rendering , tree traversing is mandatory ( see the UISitemap.gtmpl )
2. Multiple data cloning
It is better to define a filter in the UISitemap 's tree object and remove the invocation to PageNavigationUtils.filter ( analogous ideas could be found in UIFilterableTree, see GTNPORTAL-1139)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (GTNPORTAL-1314) Conflict while edit/delete and edit/move node between two or more users in Navigation management
by tung do thanh (JIRA)
Conflict while edit/delete and edit/move node between two or more users in Navigation management
-------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1314
URL: https://jira.jboss.org/browse/GTNPORTAL-1314
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: tung do thanh
Assignee: tung do thanh
1. In browser A, login with root user, go to Navigation Management, right click on a node -> edit node
2. In browser B, long in with root user (or another user), goto Navigation Management, right click on a node -> delete node -> OK -> Save
3. Back to browse A ( now, display edit node screen) , click on save -> display Navigation Management screen ->Save
-> appear Error popup message "unknow exception"; in console monitor, appear exception message (please see attach file)
It is the same if we edit/ move; delete/delete between two browsers
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months