Hi Maarten,
Yes it's true that I am now aware of a way to do this in a portal-ext.properties.
Regarding the "new way for liferay" I try to avoid to do manual configuration of the portal using the Control Panel, I prefer to automatize configuration using the portal-ext.properties as much as possible.
If I had to do such a thing I would probably tryo to set the theme porgrammatically from a hook where it is possible to select on which instance/community/... the theme will apply:
Regards,
Baptiste
Yes it's true that I am now aware of a way to do this in a portal-ext.properties.
Regarding the "new way for liferay" I try to avoid to do manual configuration of the portal using the Control Panel, I prefer to automatize configuration using the portal-ext.properties as much as possible.
If I had to do such a thing I would probably tryo to set the theme porgrammatically from a hook where it is possible to select on which instance/community/... the theme will apply:
// Set custom theme as default for private and public layouts for the Guest community
final Group group = GroupLocalServiceUtil.getGroup(companyId, GroupConstants.GUEST);
LayoutSetLocalServiceUtil.updateLookAndFeel(group.getGroupId(), false, "my_WAR_mytheme", "01", "", false);
LayoutSetLocalServiceUtil.updateLookAndFeel(group.getGroupId(), true, "my_WAR_mytheme", "01", "", false);Regards,
Baptiste
Hi Baptiste,
It's correct that the portal-ext.properties has a more strict way of configurating your portal. But on each change you have to restart and the control panel has a more unified structure.
For things like the themes, download/upload, languages, etc the control panel is much more flexible especialy when you have multiple instances.
However if you have to configure let's say the calender portlet I absolutly conclude with you because not all portlets (especialy the older portlets) can be configured from the controle panel. But this will also change with upcomming releases.
I think the only thing left to set in the portal-ext.properties in the future will be the database connection.
I guess there is no one way to do this, but a multiple ways of getting there
Regards,
Maarten
It's correct that the portal-ext.properties has a more strict way of configurating your portal. But on each change you have to restart and the control panel has a more unified structure.
For things like the themes, download/upload, languages, etc the control panel is much more flexible especialy when you have multiple instances.
However if you have to configure let's say the calender portlet I absolutly conclude with you because not all portlets (especialy the older portlets) can be configured from the controle panel. But this will also change with upcomming releases.
I think the only thing left to set in the portal-ext.properties in the future will be the database connection.
I guess there is no one way to do this, but a multiple ways of getting there
Regards,
Maarten
Hi Marteen,
My main concern with customization using in the control panel is that you have to made them manually, and they are not stored in a Source Code Management system ;)
I agree that there are multiple way of getting things done, and I hope that configuring a portal completely from the portal-ext.properties/code will still stay possible, being able to deploy a full working portal pre-configured at you will without having to login and manually do changes seems wonderful to me
For me it's more a handy way of pre-configuring a portal before deployment than reconfiguring after deployment, especially due to the need of a restart...
For daily maintenance it's sure that the Control Panel is a lot more adapted, but for a pre-deploy customization portal-ext.properties/hook is the way to go.
For now I didn't had to work with multiple-instances portal so... I know that it seems possible to have distinct portal-ext.properties per portal instance but I did not try it.
Cheers,
Baptiste
My main concern with customization using in the control panel is that you have to made them manually, and they are not stored in a Source Code Management system ;)
I agree that there are multiple way of getting things done, and I hope that configuring a portal completely from the portal-ext.properties/code will still stay possible, being able to deploy a full working portal pre-configured at you will without having to login and manually do changes seems wonderful to me
For me it's more a handy way of pre-configuring a portal before deployment than reconfiguring after deployment, especially due to the need of a restart...
For daily maintenance it's sure that the Control Panel is a lot more adapted, but for a pre-deploy customization portal-ext.properties/hook is the way to go.
For now I didn't had to work with multiple-instances portal so... I know that it seems possible to have distinct portal-ext.properties per portal instance but I did not try it.
Cheers,
Baptiste
