Possible Ways of Customizing Liferay

Possible Ways of Customizing Liferay

• Portal-ext.properties
• The portal-ext.properties file is used to override the default properties of Liferay.
• The location of the default property is “portal-impl/src/portal.properties“.
• The developer can use this file to define new properties and override existing properties.
• Language hook
• The language hook portlet can be used to update localized values of Liferay.
• Latest Liferay support language override from the control panel
• Liferay Theme
• Liferay theme is a traditional way of customizing Liferay’s look and feel.
• The latest way of changing look and feel is master layouts. client extensions and style books.
• JSP Fragment
• JSP fragments are used to customize the JSPs from the OOTB Liferay bundles.
• Using JSP fragments, we can add custom configurations in existing portlets and update the HTML code of the existing portlets.
• JSP BAG
• JSP Bag is used to customize Liferay’s core JSPs placed in Liferay’s folder “liferay/tomcat/webapps/ROOT/html“.
• Component Override
• Using the component override way, we can override any components of Liferay.
• We can do this by giving a higher service rank to the custom component.
• Liferay always uses the components with the higher service integer rank. and ignore the component with the lower version.
• Service wrapper
• Service wrappers are used to customize the logic of the Liferay service.
• Model listener
• Liferay fires events like add, update, and delete, which can be captured using model listeners.
• Model listeners are used to execute a piece of code when any of these events are fired.
• JS override
• JS override way is used to override portal JS.
• Client Extension
• Client extensions such as CSS, JS, and Favicon are used to customize the Liferay look and feel.
• Config Files
• Config files are used to override values for system-level settings.
• Events
• Liferay events like pre-login and post-login can be written to execute a piece of code when these actions are fired.
• Post-login redirection, role checking, and other business requirements can be fulfilled by these kinds of events.