Freemarker template - access to themeDisplay

[Bartlomiej Knabel, modificado hace 9 años.]

hi,

Is there any way to access ThemeDisplay object in normal freemarker template (not ADT).
Yes, I know - there is a method like ${request['theme-display']}, but it doesn't return real object (it is simple hash array)

best regards

[James Falkner, modificado hace 9 años.]

Bartlomiej Knabel:

hi,

Is there any way to access ThemeDisplay object in normal freemarker template (not ADT).
Yes, I know - there is a method like ${request['theme-display']}, but it doesn't return real object (it is simple hash array)

best regards

Unfortunately not, however you can use a trick to create a new instance and populate it with enough data to be able to use it as a real ThemeDisplay. For example, here's some code I use in a WCM template to construct a ThemeDisplay object so I can call the User.getPortraitURL() method:

<#assign portalURL = httpUtil.getProtocol(request['attributes']['CURRENT_URL']) + "://" + getterUtil.getString(request['theme-display']['portal-url']) />
<#assign mainPath = getterUtil.getString(request['theme-display']['path-main']) />

<#assign themeDisplay = objectUtil("com.liferay.portal.theme.ThemeDisplay") />
<#assign V = themeDisplay.setPathImage(getterUtil.getString(request['theme-display']['path-image'])) />
<#assign V = themeDisplay.setPathMain(getterUtil.getString(request['theme-display']['path-main'])) />
<#assign V = themeDisplay.setPortalURL(portalURL) />
<#assign V = themeDisplay.setPermissionChecker(permissionChecker) />
<#assign V = themeDisplay.setScopeGroupId(getterUtil.getLong(request['theme-display']['scope-group-id'])) />

<#assign userService = utilLocator.findUtil("com.liferay.portal.service.UserLocalService") />
<#assign user = userService.fetchUserById(getterUtil.getLong(request['theme-display']['user-id'])) />

<#assign profileUrl = user.getDisplayURL(portalURL, mainPath) />
<#assign profilePic = user.getPortraitURL(themeDisplay) />

<a href="${profileUrl}">
  <img alt="${htmlUtil.escape(user.getFullName())}" src="${profilePic}">
</a>

[Krzysztof Gołębiowski, modificado hace 9 años.]

Hi Bartłomiej and James,
I've had this issue some time ago - I don't remember what exaclty was the problem, I think we had a FOOTER article embedded using journalContentUtil and needed to use some API which required full themeDisplay/request objects. I was playing with this case for some time and finished with EXTed com.liferay.portal.templateparser.Transformer class where I had to add the following lines to transform method:

template.put("themeDisplayForWc", themeDisplay);

It is called themeDisplayForWc because as far as I remember adding new bean with key themeDisplay caused some strange problems. This solution seemed to work fine but it was so ugly and unmanageable that I decided to implement the whole functionality in different way

Regards,
KG

[James Falkner, modificado hace 9 años.]

Krzysztof Gołębiowski:

Hi Bartłomiej and James,
I've had this issue some time ago - I don't remember what exaclty was the problem, I think we had a FOOTER article embedded using journalContentUtil and needed to use some API which required full themeDisplay/request objects. I was playing with this case for some time and finished with EXTed com.liferay.portal.templateparser.Transformer class where I had to add the following lines to transform method:

template.put("themeDisplayForWc", themeDisplay);

It is called themeDisplayForWc because as far as I remember adding new bean with key themeDisplay caused some strange problems. This solution seemed to work fine but it was so ugly and unmanageable that I decided to implement the whole functionality in different way

Regards,
KG

Heh, nice According to the now-deprecated wiki page, "The processing of a template is handled in such a way that it is not dependent on access to a real HttpRequest of any kind. Why? Because it's done WITHIN the service call. We do not allow our service layer objects to have an HttpRequest or HttpResponse of any kind as parameters. Thus, we can't add any of those NON-serializable objects like ThemeDisplay"

[Alessandro Lachina, modificado hace 8 años.]

It work for me and themeDisplay is accessible.
But in catalina log I found this error:

Expression request['theme-display'] is undefined on line ..


Any idea on how to avoid it?

[Yeray Rodríguez, modificado hace 8 años.]

Alessandro Lachina:

It work for me and themeDisplay is accessible.
But in catalina log I found this error:

Expression request['theme-display'] is undefined on line ..


Any idea on how to avoid it?

Hi Alessandro,
I had the same problema. I find out that Liferay processes the template twice, the second one to get a summary of the content. The main difference is the second time Liferay doesn't pass the request object. I think the reason is the summary is not related to a real page.
To avoid the log error check request object has content.

<#if .vars['request']?has_content>
<#-- code which use request objects -->
For instance: ${request.secure}
<!--#if-->

[Traolly Xiong, modificado hace 8 años.]

Hello Yeray,
I am getting the same error, but this occurs on the staging site page.

Expression request['theme-display'] is undefined on line 42, column 62 in 10154#10192#4762100.

The object works fine on my local machine, but not on our DEV server.

Any thoughts?

Thanks.

[Igor Kanshyn, modificado hace 7 años.]

Hi,

I'm trying to use

<#assign portalURL = httpUtil.getProtocol(request['attributes']['CURRENT_URL']) + "://" + getterUtil.getString(request['theme-display']['portal-url']) />

but getting error:
request['attributes'] is undefined
I'm in web content FreeMarker template on Liferay 6.2

Any ideas why request['attributes'] is not available for me?

[Shubhankit Roy, modificado hace 7 años.]

Try using this:

<#assign serviceContext = staticUtil["com.liferay.portal.service.ServiceContextThreadLocal"].getServiceContext()>
<#assign themeDisplay = serviceContext.getThemeDisplay() />

[Alessandro Lachina, modificado hace 7 años.]

great! it works

[Alessandro Candini, modificado hace 6 años.]

Shubhankit Roy:

Try using this:

<#assign serviceContext = staticUtil["com.liferay.portal.service.ServiceContextThreadLocal"].getServiceContext()>
<#assign themeDisplay = serviceContext.getThemeDisplay() />

This is the way, with Liferay 7 too!

Thank you so much!

[Massimo Bevilacqua, modificado hace 6 años.]

In liferay 7 the class is:

com.liferay.portal.kernel.service.ServiceContextThreadLocal

and not:

com.liferay.portal.service.ServiceContextThreadLocal

[Achmed Tyrannus Albab, modificado hace 6 años.]

Shubhankit Roy:

Try using this:

<#assign serviceContext = staticUtil["com.liferay.portal.service.ServiceContextThreadLocal"].getServiceContext()>
<#assign themeDisplay = serviceContext.getThemeDisplay() />

<#assign imagesPath = getterUtil.getString(request['theme-display']['path-theme-images']) />
${imagesPath} gets me /theme-directory/image-directory .

<#assign mainPath = getterUtil.getString(request['theme-display']['path-main']) />
${mainPath} gets me com.liferay.portal.theme.ThemeDisplay@4d91e899

which is the same with what youve provided.

What i want is just /theme-directory/ and thats it.
How do i get this?