Hi folks! On a standard Liferay Installation you place the portal-ext.properties file one folder above the tomcat folder. In this file, you overwrite the default settings from ROOT/WEB-INF/classes/portal-ext.properties. However, if I place the portal-ext.properties file in the folder: /opt/bitnami/apps/liferay/data where the file portal-setup-wizard.properties resides (which is on a standard installation the same directory where you place portal-ext.properties) it will not get loaded. I really have a Problem whith editing the portal-ext.properties file in ROOT/WEB-INF/classes/ as if you work with EXT-PLugins, and you need to redeploy it, you have to delete the ROOT folder, and extract it from the bundle agaiun, to get the initial state of the Portal. This would also overwrite portal-ext.properties along with all modifications made there. Any help would be really appreciated. Thanks a lot Jan
Ok. I put the entries I previously had in the portal-ext.properties file in portal-setup-wizard.properties and this seems to work.
Even though any kind of information on this topic would have been nice ;)
Thanks for sharing your solution. We ship Liferay already deployed so we can use the portal-ext.properties in the WEB-INF/classes folder. This is the standard way, if you want to customize these settings you can add in the portal-setup-wizard.properties file as you mention.
Well, here are some more thoughts why the way you are shipping your custom portal-ext.properties file in the ROOT folder is NOT a good idea. If you deploy an EXT plugin, which modifies the Portal Source itself, and you ship portal.properties with it, the portal-ext.properties file will get overridden and all the customization you have done are lost. If you redeploy an Ext Plugin you will have to delete the whole ROOT Folder and start with a fresh install. This will result in the loss of the portal-ext.properties file as well. You would have to have the foresight, to backup the ROOT folder of your installation. To be honest: I didnt and started swearing. Wouldn't it be better, if you leave the property files at the location and include the include-and-overwrite directive in there? Just a few thoughts. No offence intended ;)
And another Thing: in your portal-ext.properties is the directive: resource.repositories.root=/opt/bitnami/apps/liferay/data which leads to the following: the directory for the document_library would be: /opt/bitnami/apps/liferay/data/data I think this is a slight mistake there ;)
Thanks for your further thoughts and explanations. We will take a look at the current approach and try to find a better implementation to make easier the upgrade process.
Hi, I totally agree with GevatterJan, This is an old thread but it seems nothing has changed. I’m using a bitnami image with liferay-6.2.5-1. Am I wrong?
I found a solution by myself, inserting in portal-setup-wizard.properties the following:
where “myfile.properties” is my own file in /opt/bitnami/apps/liferay/data/
Note: I use liferay-6.2.5-1
Thanks @vincenzo_cerbone for your fix
Javier J. Salmerón