Properties to disable User private pages.

After a bit of struggle I found that to disable private pages of users in Liferay these properties can be applied in the portal-ext.properties file:


layout.user.private.layouts.enabled=false
layout.user.private.layouts.modifiable=false
layout.user.private.layouts.auto.create=false

layout.user.public.layouts.enabled=false
layout.user.public.layouts.modifiable=false
layout.user.public.layouts.auto.create=false



I also tried to apply theme to these private pages by these properties:


layout.user.public.layouts.enabled=true
layout.user.private.layouts.enabled=true
default.user.private.layout.regular.theme.id=iconnect_WAR_iconnecttheme
default.user.public.layout.regular.theme.id=iconnect_WAR_iconnecttheme
layout.user.private.layouts.auto.create=false
layout.user.public.layouts.auto.create=false

However these properties intermittently showed user private pages without the specified theme. I am not sure about the reason, but I suspected the users were probably trying something funny by creating their own pages and playing around with it. So I decided to disable the pages altogether. No pages is better than having pages without Theme ;) at least that's how it was in my case..

Comments

Post a Comment

Popular posts from this blog

jQgrid reload with new data

To reload a jQGrid with fresh data you need to set the data parameter on the grid and invoke reload on it. jQuery("#promotionsGrid").setGridParam({ 'data': newData}).trigger("reloadGrid"); Here newData is a JavaScript array with which I need to re-load the grid. The important thing here is that I had to place this statement just before the grid initialization code even though the reload was expected on change event of a text box. Without that there was simply no effect on my grid!
Read more

Rich Client based UI technologies- A Comparison of Thick Client UI tools

Rich Client v/s Thin Client Software developers face many difficult decisions when building new applications, not the least of which is graphical user interface. There are various graphical user interface technologies used, but broadly they can be classified as Rich Client User interfaces and the thin client or web based user interfaces. To understand them better let us look at the history of rich and thin clients. While the Rich client GUI applications would support high quality end-user experience with features such a drag-and-drop, perspectives, customization, high speed local processing; it has had a traditional disadvantage of high deployment and upgrade costs. It was becoming highly difficult and costly to deploy and upgrade these applications. Then came the thin clients or the Web based applications. Thin clients solved many of the deployment and upgrade problems, but that was not without a cost, the cost was in terms of functionality and capability. Thin clients, based on
Read more

OSS and BSS Systems

Image
OSS (Operational Support Systems) Software (occasionally hardware) applications that support back-office activities which operate a telco’s network, provision and maintain customer services. OSS is traditionally used by network planners, operations, architects, support, and engineering teams in the service provider. Increasingly product managers and senior staff under the CTO or COO may also use or rely on OSS to some extent. BSS (Business Support Systems) Software applications that support customer-facing activities. Billing, order management, customer relationship management, call centre automation, are all BSS applications. BSS may also encompass the customer-facing veneer of OSS application such as trouble-ticketing and service assurance – these are back-office activities but initiated directly by contact with the customer. OSS/BSS Structure Communication between OSS and BSS Apart from service assurance activities being cross-OSS-BSS processes, there are as m
Read more