Sachin Jagtap

In Liferay 6.2 version, Liferay introduced a very good feature that’s Application Display Template ( ADT ). Using ADT, we can overcome creating a JSP hooks customization in Liferay portal. Before Liferay 6.2, If we needed to change the look and feel of OOBT portlets like below listed,           Blogs, Documents and Media, Wiki Map, Message Board etc. Then we have go with JSP Hook Customization or we can’t do the look and feel changes on fly. But Using ADT we can achieve this. The Following portlets come with ADT functionality. i.       Asset Publisher ii.     Blogs iii.   Document and Media iv.   Categories Navigation v.     Tags Navigation vi.   Wiki vii. Site Map

Liferay portal provides multilingual support of 34 languages for OOBT portlets. Below are the listed locale(languages) liferay provides supports for OOBT portlets, Arabic (Saudi Arabia) - ar_SA Basque (Spain) - eu_ES Bulgarian (Bulgaria) - bg_BG Catalan (Andorra) - ca_AD Catalan (Spain) - ca_ES Chinese (China) - zh_CN Chinese (Taiwan) - zh_TW Czech (Czech Republic) - cs_CZ Dutch (Netherlands) - nl_NL English (United States) - en_US Estonian (Estonia) - et_EE Finnish (Finland) - fi_FI French (France) - fr_FR galician (Spain) gl_ES German (Germany) - de_DE Greek (Greece) - el_GR Hebrew (Israel) - iw_IL Hindi (India) - hi_IN Hungarian (Hungary)- hu_HU Italian (Italy) - it_IT Japanese (Japan)- ja_JP Korean (South Korea) - ko_KR Norwegian - nb_NO Farsi/Persian (Iran) - fa_IR Polish (Poland) - pl_PL Portuguese (Brazil) - pt_BR Portuguese (Portugal) - pt_PT Russian (Russia) - ru_RU Slovak (Slovakia) - sk_SK Spanish (Spain) - es_ES Swedish (Sweden)...

Internalization (I18N) Support for Liferay custom plugin content. Sometime client has a requirement is like to support multilingual for custom modules. In Requirement In custom portlet has a one from which will submit with different-different languages. Like Web content, Polls, Workflows in Liferay etc. When users view the submitted details or Client wants to showcase the submitted information to users based on user’s locales then the display portlets will automatically rendered into user’s selected locale (language).           How to support Internalization (I18N) to text field & Text Editors in custom portlets? ·            Liferay has implanted such functionality in Polls, Web contents, Pages creations time ... ·          Through <liferay-ui:input-localized > we can achieve for custom portlet also.       ...

          Introduction               If we need to export Liferay calendar events with Outlook & Google calendar then we need to configure .ics file and if requirement is export and auto sync up then we need .ics file to be downloaded from source portal. For example:   webcal://abc.com/abcCalendar.ics   or   http://www.abc.com/abcCalendar.ics   etc,    then we can configure the outlook Internet Calendar configuration and Google Calendar configuration or any other calendar applications portals using downloaded URL.     What is an .ICS file?                    Files that contain the .ics file extension are created by a variety of calendar and scheduling applications. These calendar files allow different users to store calendar information within a text file. That text file c...