Liferay.Language.get("my.key")) returns "my.key" instead of value

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.0 CE RC1
• Fix Version/s: None
• Component/s: UI, UI > JavaScript & CSS
• Labels: None
• Environment: LR Revision 69944 , Firefox, chrome, opera
• Similar Issues: Show 5 results ; ;

  LPS-27187	HitsImpl.getLength() returns wrong value
  LPS-14551	InputPermissionsParamsTagUtil.getDefaultViewRole returns wrong value
  LPS-28819	LayoutImpl can Return incorrect Theme Setting
  LPS-28820	LayoutImpl can Return incorrect Theme Setting
  LPS-663	SAWServletContextListener._getCurrentClassLoader returns the LR-CL instead of saw-web CL

Hi, localization via liferay-ui:message works fine for me, but Liferay.Language.get( ) does not. I always get a response with the "key" instead of "value". So that

Liferay.Language.get("my.key")) returns "my.key"

I spent 2 hours already figuring that out, but without success. I checked it is the correct locale.

[Jakub Liska]

It is most likely not possible for portlet context.

see : http://www.liferay.com/community/forums/-/message_boards/message/7044586

[Oleksandr Maksymchuk]

Liferay.Language.get("my-key") works for me in my portlet on v6.0.5 without problem,

Note I have:
<resource-bundle>content.myportletid.Language</resource-bundle>
specified in portlet.xml or the portlet itself.

Although what I want to do is to move some javascripts to portal level (ext plugin) and reference them from portlet as:

<header-portal-javascript>/html/js/yui2/yui2-dom.js</header-portal-javascript>

This works, but now Liferay.Language.get("my-key") outputs "my-key".
I've tried to add appropriate message to my

my-ext/docroot/WEB-INF/ext-impl/classes/content/Language-ext.properties

but this doesn't have any effect.

I understand the reported bug may be only 6.1.x related, but what I'm reporting has the same results, so hope there is some common ground between them.

[Oleksandr Maksymchuk]

My problem was due to caching. I actually had to redeploy portlet additionally to the my-ext plugin which contained common Language-ext.properties for they to be affective (e.g. applied onto javascripts in portlet). My error was that I was 'just' redeploying my-ext and restarting the tomcat.

[James Falkner]

So it sounds like your issues is resolved, so I am closing this. If you feel there is a bug here, feel free to re-open. Thanks!

[Oleksandr Maksymchuk]

Well, the original issue was not mine. And I didn't test against v6.1.X. So maybe it is still actual. Reporter should comment on this in this case.

[Jakub Liska]

Guys it really doesn't work for me. It works fine when calling Portal context, but not portlet context. There is nothing to be misconfigured as to resource bundles in my case. It is pretty straightforward. The only plugin where this is used is Mail plugin. It obviously work there, but I'm thinking whether there is something that must be done for it to work. Because setting up portlet.xml for portlet localization works only for JSP tag liferay-ui:message. The javascript calls don't get into my portlet context.

[Jakub Liska]

I had some time to come back to it. The problem is, that after the request hits LanguageServlet and its "LanguageUtil.get(locale, key);" method, in LanguageImpl class, there is following snippet of code, that takes care of loading portlet properties :

portletConfig = (PortletConfig)request.getAttribute(JavaConstants.JAVAX_PORTLET_CONFIG);

if (portletConfig != null) {
ResourceBundle resourceBundle = portletConfig.getResourceBundle(locale);

try

{ value = resourceBundle.getString(key); }

But portletConfig is null...in that case it searches through portal Language resources only, otherwise returns the "key" value... I sense it could be problem in 6.1.x LR version

[Jakub Liska]

Omg this issue makes me crazy.

I just tested the Mail-portlet, and there is main.js that contains "Liferay.Language.get('add-account')" for instance, when add account button is clicked (the dialog is localized). The LanguageServlet should get called as in case of my portlet, but it is not (I have a breakpoint there) and despite it, the message is localized, what kind of magic is this...

[Jakub Liska]

http://www.liferay.com/community/forums/-/message_boards/message/7593698

[Jakub Liska]

RESOLVED: http://issues.liferay.com/browse/LPS-16513