[JBoss JIRA] (GTNPORTAL-2374) Portlet edit mode css are broken in the page editor
by donino doninos (JIRA)
donino doninos created GTNPORTAL-2374:
-----------------------------------------
Summary: Portlet edit mode css are broken in the page editor
Key: GTNPORTAL-2374
URL: https://issues.jboss.org/browse/GTNPORTAL-2374
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PC integration, User Interface
Affects Versions: 3.2.0-GA, 3.2.0-CR01
Environment: Tested on Linux Ubuntu, Windows 7, Windows server 2003 with tomcat 6 & 7 and jboss 6
Reporter: donino doninos
Assignee: Matt Wringe
The custom 286 Portlets use the doHeaders method to include the required css and javascript files. It works both in view mode and in edit mode in the standard portlet windows, but in the page editor the css/js are broken, therefore the edit mode cannot be displayed correctly.
If the css/js are directly included in the jsp files then it works. Currently in order to work in any portal sections, it seems the resource files need to be included both in the doHeaders method and in jsp files, whereas the doHeaders include should be sufficient.
--
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, 1 month
[JBoss JIRA] Created: (GTNPORTAL-1791) Incorrect logging category in CacheUserProfileFitler
by Marek Posolda (JIRA)
Incorrect logging category in CacheUserProfileFitler
----------------------------------------------------
Key: GTNPORTAL-1791
URL: https://issues.jboss.org/browse/GTNPORTAL-1791
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1.0-GA
Environment: Gatein trunk, revision 5668
Reporter: Marek Posolda
Priority: Trivial
In class org.exoplatform.web.CacheUserProfileFilter is incorrect logging category
private static Log log = ExoLogger.getLogger("core.security.SetCurrentIdentityFilter");
This causes confusing exception messages, which seems to be thrown from SetCurrentIdentityFilter even if they are thrown from CacheUserProfileFilter like:
[SetCurrentIdentityFilter]An error occured while cache user profile
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month