Working with Alloy UI Taglibs

-
We can use readly avalible taglibs in our customportlet , Here are the some

1. If we want user to rate the content we can use "ratings" taglib as,

<liferay-ui:ratings classPK="12724" className="<%=BlogsEntry.class.getName() %>"></liferay-ui:ratings>



Here classPK is the  primarykey , here i am using the blogsentry so it is blogsentryid
className is the classname of the entry, wheather it is "BlogsEntry" , "JournalArticle" etc.







2. If we want to display the rating score

<liferay-ui:ratings-score score="2"></liferay-ui:ratings-score>





3. "Discussion" taglib mostly used to display the user comments

<liferay-ui:discussion classPK="12724" userId="10201" className="<%=BlogsEntry.class.getName() %>" formAction="fm"></liferay-ui:discussion>

Here classPK is the  primarykey , here i am using the blogsentry so it is blogsentryid userId is the userId of the user
    className is the classname of the entry, wheather it is "BlogsEntry" , "JournalArticle" etc.



4. This is useful to report the content as spam
  <liferay-ui:flags reportedUserId="10201" classPK="12724" contentTitle="contentTitle" className="<%=BlogsEntry.class.getName() %>"></liferay-ui:flags>


    Here reportedUserId is the userId of the user
    classPK is the  primarykey , here i am using the blogsentry so it is blogsentryid
    className is the classname of the entry, wheather it is "BlogsEntry" , "JournalArticle" etc.




5.  This is used to display the header
     <liferay-ui:header title="This header"></liferay-ui:header>




6.   This is also widely used taglib to add the tags for the content.
    <liferay-ui:asset-tags-selector></liferay-ui:asset-tags-selector>




7.  This is useful to display the content in the tabs
   <liferay-ui:tabs names="table"></liferay-ui:tabs>




8. This is useful to display the date in the textbox
   <liferay-ui:input-date dayValue="04" monthValue="04" yearValue="1988"> </liferay-ui:input-date>

    here is have provided some value to display the date so it takes as May 05th 1988.




9. This is used to display the calendar
<liferay-ui:calendar month="09" year="2015" day="06" showAllPotentialWeeks="true"  headerPattern="dd/mm/yyyy"></liferay-ui:calendar>



Comments

  1. james_lopezMarch 26, 2016 at 12:25 PM

    Its a worthy post and rare information too. and i could expect if you're an expert on this place of interest. Well collectively with your authorization i want to00 grab your feed to be upgraded with up and coming post. You can easily take this kochi to munnar taxi for any excursions and travels program of your family. They will be providing secured and secure cabs.

    ReplyDelete

Post a Comment

Popular posts from this blog

Theme display in javascript

-
We know that we can access the themedisplay in java as ThemeDisplay themeDisplay = (ThemeDisplay) request.getAttribute(WebKeys.THEME_DISPLAY) But how can we access in javascript? Here we go Liferay.ThemeDisplay.getScopeGroupId() Liferay.ThemeDisplay.getCompanyId() Liferay.ThemeDisplay.getPlid() Liferay.ThemeDisplay.getLayoutId() By this we can access the groupId, companyid ... etc
Read more

How to know which liferay version we are using

-
Image
Sometimes we have to know which liferay version we are using, so how can we know? We can know the liferay version in different ways. 1. Liferay has provided some utility methods to know the which liferay version we are using , Here is the utility method ReleaseInfo.getReleaseInfo() It prints this statement " Liferay Portal Community Edition 6.2 CE GA2 (Newton / Build 6201 / March 20, 2014) " as i am using community version it shoes as CE. 2. Also we can also identify by response headers as below screenshot. If your using the chrome, right click on the browser and click inscept element , and navigate to the network  . you will see the URLS , click on the any url. 3. Also we can see during server startup as below statement Liferay Portal Community Edition 6.2 CE GA2 (Newton / Build 6201 / March 20, 2014)
Read more

Viewing the SQL Query in liferay : debugging the SQL Query in Hibernate

-
Sometimes we have to know SQL query hiting in DB to retrieve the list. Suppose When we are writing the DynamicQuery , Some times we have to know SQL query it is generating to hit DB. So generally it is useful when we are debugging the Query it is generated. In hibernate we used the write the property in XML file as hibernate.show.sql to view the query. In Liferay also we can also set the below property to true in the portal-ext.properties to view the SQL query at the console. hibernate.show_sql=true. By adding the above property it will just reterive the parameters. What if we want to display the parameters. Add the below properties in log4j.properties it will display the paramters also. # logs the SQL statements #log4j.logger.org.hibernate.SQL=debug # Logs the JDBC parameters passed to a query #log4j.logger.org.hibernate.type=trace In Liferay log4j is located in the below location tomcat-7.0.42\webapps\ROOT\WEB-INF\classes Also we want to see hibernate ses
Read more