Bug 793400 (JBEPP-482) - Page's title and portlet's title are not localizable
Summary: Page's title and portlet's title are not localizable
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-482
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.ER01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER02
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-23 08:08 UTC by Thomas Heute
Modified: 2018-11-30 19:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-23 09:35:16 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-1379 0 Major Resolved Page's title and portlet's title are not localizable 2013-04-05 08:26:59 UTC
Red Hat Issue Tracker JBEPP-482 0 Major Closed Page's title and portlet's title are not localizable 2013-04-05 08:26:59 UTC

Description Thomas Heute 2010-09-23 08:08:12 UTC
project_key: JBEPP

Comment 1 Thomas Heute 2010-09-23 08:08:28 UTC
Link: Added: This issue is related to GTNPORTAL-1379


Comment 2 Scott Mumford 2010-11-10 02:10:56 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: Page and portlet titles were not localizable in previous releases of EPP
These titles can now be localized either through keys in pages.xml or via the administration interface.


Comment 3 Adam Kovari 2013-02-28 08:46:41 UTC
Hello,

in what version is this scheduled to be fixed?

In JPP 6 beta it seems to be still reproducable:

Step to reproduce :
- Edit the pages.xml of the classic portal
- Change the page title with #{portal.classic.home}
- Start the server with a clean jcr

Result:
- #{portal.classic.home} is display on page title instead of the 
"Home" label define in classic.properties ressource bundle.


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