[ http://issues.apache.org/jira/browse/JS2-321?page=comments#action_12317529 ]
Santiago Gala commented on JS2-321: ----------------------------------- My experience with those errors you mention is that they disappear by reloading. I'm seeing several problems related with too much caching (maybe in mod_proxy, which I'm using to proxy requests to tomcat). Minor ones, not sure if this one is of this type. It is like if, after coming back from edit to view mode, the page displayed is the old one, or, more probably, uses the old layout w/o the changes. > Customizer not correctly positoning portlets > -------------------------------------------- > > Key: JS2-321 > URL: http://issues.apache.org/jira/browse/JS2-321 > Project: Jetspeed 2 > Type: Bug > Components: Customizer, Layout > Versions: 2.0-M1, 2.0-M2, 2.0-M3, 2.0-M4 > Reporter: Scott T Weaver > Assignee: Scott T Weaver > Fix For: 2.0-M4, 2.0-FINAL > > It appears that the positioning in the customizer is still not correctly > updating postions for moved fragments after returning for edit mode in a > layout. Also, all the positioning code lies withing the MultiColumnPortlet > itself and would be better served if it were moved out into a seperate, > easily teastable model object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
