Liferay: How to configure Liferay Portal

Question

How to configure or to override Liferay portal properties with portal.properties?

Answer 1

Yes whenever we override the liferay property by using liferay.properties file we create a file called lifery-ext.properties file and then we add over requirement inside this folder and our liferay use this file and whatever modification you performed here(liferay-ext.properties file) will reflect in your liferay setting. Thanks asif aftab

Answer 2

You can override portal properties which are present in portal.properties file. Using creating portal-ext.properties file which can be placed in portal-home/webapp/root/web-inf/classes folder. for ex: ../liferay-portal-x-ce-ga2\tomcat-x.0\webapps\ROOT\WEB-INF\classes

in this location you can keep portal-ext.properties file which ever properties you want to override you can override.

Answer 3

Do not edit the portal.properties file. If you want to override any of the property, if not exists portel-ext.properties file in your liferay_home or ROOT/classes folder then create portel-ext.properties file in liferay_home and add your property entry in it. Restart server to see changes.

See all properties you can override portal-ext.properties

Answer 4

Dont edit the portal.properties file. You can override portal.properties file making a copy and rename portal-ext.properties, which must be placed in liferay_home/portal-ext.properties

You can configure the properties in the control panel, but if you configure using both methods and there's a property conflict, the control panel settings take precedence.

Answer 5

you can override portal.properties by using hook or EXT. You can create portal-ext.properties file and put it into WEB-INF/classes folder in hook and can deploy that hook. In portal-ext.properties you can override all the properties of portal.propertis file

Answer 6

Remember that when you edit portal properties in the GUI (Control Panel -> Configuration -> Portal Settings), these changes take preference over whatever you have in portal-ext.properties. So if you have, let's say, a default landing page specified in Portal Settings, whatever value you put in portal-ext.properties (default.landing.page.path=/your/path) is ignored.