Bug 793511 (JBEPP-592) - Banner and footer portlets - template preference
Summary: Banner and footer portlets - template preference
Keywords:
Status: CLOSED WONTFIX
Alias: JBEPP-592
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.ER03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-29 12:17 UTC by Michal Vanco
Modified: 2013-04-30 23:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 11:48:42 UTC
Type: Feature Request


Attachments (Terms of Use)
banner_and_footer_preferences.png (57.10 KB, image/png)
2010-10-29 12:18 UTC, Michal Vanco
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-592 0 Major Closed Banner and footer portlets - template preference 2012-07-13 12:35:48 UTC

Description Michal Vanco 2010-10-29 12:17:21 UTC
project_key: JBEPP

In classic portal there are banner and footer portlets by default.

If you click edit layout and edit any of these portlets -> it has Preferences tab with Template.
If you change value of template to anything -> nothing happens.

Btw. if I add banner or footer portlet on some page and Edit page + edit portlet, it doesn't have Preferences tab anymore.

Another example:
- Breadcrumbs portlets has two preferences as well, but when I edit this porltet in layout -> there is no Preferences tab.

Comment 1 Michal Vanco 2010-10-29 12:18:25 UTC
Attachment: Added: banner_and_footer_preferences.png


Comment 2 Michal Vanco 2010-10-29 12:25:07 UTC
Sorry, there is one change.

If you change Template value it take effect, but after signing out.

So this should be changed immediately. And what about some validation of Template input? Is it possible so that it could validate template path?

Comment 3 Michal Vanco 2010-10-29 12:38:16 UTC
One more comment:
- if you change value of footer portlet from par:/groovy/groovy/webui/component/UIFooterPortlet.gtmpl to "text in footer"
- it is saved properly, finish Edit Layout
- sign out
Error in log:
08:36:29,140 ERROR [FutureCache] Computing of resource org.exoplatform.resolver.ResourceKey@d2ace7e5 threw an exception
java.lang.NullPointerException: No null input stream accepted
	at org.exoplatform.commons.utils.IOUtil.getStreamContentAsBytes(IOUtil.java:153)
	at org.exoplatform.groovyscript.text.TemplateService$1.retrieve(TemplateService.java:76)
	at org.exoplatform.groovyscript.text.TemplateService$1.retrieve(TemplateService.java:69)
	at org.exoplatform.commons.cache.future.FutureCache$1.call(FutureCache.java:83)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at org.exoplatform.commons.cache.future.FutureCache.get(FutureCache.java:117)
	at org.exoplatform.groovyscript.text.TemplateService.getTemplate(TemplateService.java:154)
...
08:36:29,142 ERROR [portal:Lifecycle] Template: text in footer not found.

Comment 4 Scott Mumford 2010-11-08 09:12:35 UTC
Release Notes Docs Status: Removed: Not Required Added: Documented as Known Issue
Release Notes Text: Added: Editing the Template field of the banner or footer portlet preferences to any non-default value can result in changes not being validated as the portlets, by default, require a groovy template.


Comment 5 Thomas Heute 2010-11-09 08:37:37 UTC
More a feature request rather than a bug, not assigning to any particular release. No need for release note

Comment 6 Thomas Heute 2010-11-09 08:37:37 UTC
Release Notes Docs Status: Removed: Documented as Known Issue Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.