Practical people. Practical problems. Practical advice.

Posts in category Liferay

Liferay – Get group or community details in theme.

May12
2012 Leave a Comment Written by Liferay PLA

This can be accomplished by using the velocity method $theme_display.getScopeGroup() in the theme. This method can be assigned to an velocity variable either in the init_custom.vm or portal_normal.vm based upon the developer’s convenience.

 #set ($thisScopeGroup = $theme_display.getScopeGroup())

$thisScopeGroup

This would provide all the group details as below:

 {groupId=27518, companyId=10201, creatorUserId=15402, classNameId=10021, classPK=27518, parentGroupId=0, liveGroupId=0, name=Another Group, description=Just another group or community, type=2, typeSettings=, friendlyURL=/new-group, active=true}

To get an individual detail such as groupId, we could simply use $thisScopeGroup.getGroupId() ($thisScopeGroup is defined above) and assign it to a velocity variable as:

#set ($scopeGroupId = $thisScopeGroup.getGroupId())

This would output only the group Id and can be used for further manipulations.

Tagged , , , , ,

Liferay Themes – ecomware

May09
2012 Leave a Comment Written by ecomware

We Ain’t Selling Out!

Yesterday, we got an offer. Our tiny domain has attracted attention because it dominates major keyword phrases for Liferay, the Enterprise open source portal and collaboration software. Even though we’re not officially among the Liferay Service Partners *, developers from around the world know ecomware for its several basic tutorials on structures and themes. Apparently, it occurred to someone that ecomware might be a valuable addition to their online real estate portfolio. But we’re not yet ready for that. We’re happy serving multiple developer (user and small business) communities. We appreciate the people who look to ecomware for tips and tricks, and we thank you for making ecomware a well-respected site around the world!

Not Connected, Just Knowledgeable

* We’re not affiliated with the Liferay gang in any way. We’re just community members. We published our tutorials on the platform before much documentation existed, and for that we were rewarded with plenty of visits from curious Liferay programmers over the last few years.

Posted in Babble - Tagged , , ,

Liferay Properties File

Apr27
2012 Leave a Comment Written by Liferay PLA

Having variables defined in the properties file and accessing them through the theme helps immensely when we are dealing with language and environment specific content. This can be achieved as follows:

The properties file in liferay is basically an index of innumerable key value pairs.
Consider the url ‘www.abc.com’ (value) defined in the properties file attached to the key ‘abc’ as
abc=www.abc.com

In portal_normal.vm or init_custom.vm, we declare a velocity variable ‘abclink’ and link it to the key in properties file as
#set ($abcurl= $propsUtil.get(‘abclink’))

We can now use this variable all across the theme wherever we want.
Example: Replace $abcurl  as the href attribute for the anchor tag where the link will be used.

Posted in Code - Tagged , , , ,

Liferay Dock

Apr18
2012 Leave a Comment Written by Liferay PLA

Display dockbar only to admin and/or specific user roles.
This can be done in two ways. Add the below code in portal_normal.vm
1st Method:

#if($is_signed_in && $permissionChecker.isCompanyAdmin($company_id))
#dockbar()
#end

2nd Method:

#*  ROLE CHECKING  *#
#set ($uRoles = $themeDisplay.getUser().getRoles())
      #foreach ($role in $uRoles)
          #set ($roleName = $role.getName())
          #if ($roleName == "Administrator")
               #set ($adminUser = "true")
          #end
      #end
#if($adminUser)
    #dockbar()
#end

The 1st method allows us to display the dockbar (which can be replaced by any specific content) only to the admin user role, while the 2nd method checks for a specific user role and displays the required content.

P.S: The dockbar display code is for Liferay v 6.x.x. For Liferay v 5.x.x replace

#dockbar()

with

#parse ("$full_templates_path/dock.vm")
Posted in Code - Tagged , , , , , ,

Liferay Consulting

Apr11
2012 Leave a Comment Written by ecomware

ecomware garnered a lot of visitors by its connection with Liferay, and specifically for demonstrating themes, layouts and the cool tricks you can perform using templates and structures. ecomware started off as a private collection of development notes, and we wrote the Liferay articles while developing the UI for a top-10,000-ranked, US-based ecommerce site. There was little documentation available on creating extremely dynamic themes at the time, and ecomware quickly gained a top spot for keyword searches. We still rank impressively high for the simple search: “liferay structures“.

Our audience and our purpose have changed, and our appearance will change in the near future too. But we would still like to serve the Liferay community. If you need help with a previous post, or would like to work with ecomware on a current Liferay project, please email us at smb@ecomware.com. Of course, you may also post questions on respective posts–we’ll do our best to support those that seek clarity or spur meaningful discussion about UI development techniques in Liferay.

Posted in Site Updates - Tagged , , ,

Layout Type Portlet or getProperty

Feb01
2011 Leave a Comment Written by ecomware

I do prefer the following method over $themeDisplay.getLayoutTypePortlet().getLayoutTemplateId(), and it has other good uses.

#set ($layoutID = "$layout.getTypeSettingsProperties().getProperty('layout-template-id')")
Posted in Code

liferay-look-and-feel.xml

Jan27
2011 Leave a Comment Written by ecomware 
<!DOCTYPE look-and-feel PUBLIC
    "-//Liferay//DTD Look and Feel 6.0.0//EN"
    "http://www.liferay.com/dtd/liferay-look-and-feel_6_0_0.dtd">
<look-and-feel>

    <compatibility>
        <version>6.0.5+</version> <!-- VERSION, Compatibility is a required element -->
    </compatibility>
    <theme id="set" name="set">
        <settings>
            <!-- NOTE THE COOL PROPERTY SETTING -->
            <setting key="portlet-setup-show-borders-default" value="false" />
        </settings>
    </theme>
    <theme id="spike" name="spike">
        <settings>
            <setting key="portlet-setup-show-borders-default" value="false" />
        </settings>
    </theme>

</look-and-feel>
<!-- GET THE THEME NAME
 $themeDisplay.getTheme().getName()
-->
Posted in Code, XML and XSLT Examples

liferay-layout-templates.xml

Nov09
2010 Leave a Comment Written by ecomware 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE layout-templates PUBLIC "-//Liferay//DTD Layout Templates 6.0.0//EN" "http://www.liferay.com/dtd/liferay-layout-templates_6_0_0.dtd">

<layout-templates>
    <custom>
        <layout-template id="ngw_nav_1_col" name="ngw_nav_1_col">
            <template-path>/ngw_nav_1_col.tpl</template-path>
            <wap-template-path>/ngw_layout_group.wap.tpl</wap-template-path>
            <thumbnail-path>/ngw_layout_group.png</thumbnail-path>
        </layout-template>
        <!--
        <layout-template id="ngw_layout_group" name="ngw-layout-group">
            <template-path>/ngw_layout_group.tpl</template-path>
            <wap-template-path>/ngw_layout_group.wap.tpl</wap-template-path>
            <thumbnail-path>/ngw_layout_group.png</thumbnail-path>
        </layout-template>
        -->
    </custom>
</layout-templates>
Posted in Code, XML and XSLT Examples

liferay-hook.xml

Nov09
2010 Leave a Comment Written by ecomware 
<?xml version="1.0"?>
<!DOCTYPE hook PUBLIC "-//Liferay//DTD Hook 6.0.0//EN" "http://www.liferay.com/dtd/liferay-hook_6_0_0.dtd">
<hook>
    <custom-jsp-dir>
        /META-INF/ngw_layout_velocity_templates/
    </custom-jsp-dir>
</hook>
Posted in Code, XML and XSLT Examples

Liferay 6 Custom Fields with Velocity

Oct26
2010 Leave a Comment Written by ecomware

Adding a Custom Field to the Page resource in Liferay 6 seems like a great way to add page-specific attributes – css classes, maybe, or a key for the application of some hash-based storage. It sure seems intuitive that those fields would then be accessible from velocity, where the page-level attributes could really be put to use. And they are available, but it isn’t immediately obvious how to get them.

Here is how you can access custom fields that have been set for the page resource.

$navItems.get($index).getLayout().getExpandoBridge().getAttribute("pageid")
##OR
$themeDisplay.getLayout().getExpandoBridge().getAttribute("pageid")
##OR
$layout.getExpandoBridge().getAttribute("pageid")

If you add the Custom Field “pageid” to the resource Page, then the respective values of pageid will be accessible through each page’s corresponding nav item.

For example, let’s say we added pageid as a custom field (of type text). Then, for /web/guest/home, we can simply go to Manage -> Page, and edit the pageid field to say “Hello, Custom Field!”. Now we can retrieve the value “Hello, Custom Field!” this way:

## ...included in portal_normal.vm, for example...
#foreach ($navItem in $navItems)
	#if ($navItem.isSelected() == "true")
		#set ($pageID = $navItem.getLayout().getExpandoBridge().getAttribute("pageid"))
	#end
#end
<h3>$pageID</h3>

Here is how you can access custom fields that have been set for the user resource.

$themeDisplay.getUser().getExpandoBridge().getAttribute('attributeName')
Posted in Code
← Older Entries