• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

is there a role based control of private or public layouts in Liferay?

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

For a company portal I would like to setup with:
- public users which access the pages of the website, they would not have public pages and may have (not decided yet) private pages but unmodifiable
- company users will have at least one group where will be the intranet, those users will not have public pages and their private pages is modifiable
- a category of company users (or groups) which are allowed to have public pages and modifiable private pages
- at least one customer group, they would not have public pages and their private pages has to be unmodifiable. The customer related group stands for customer support and there will be a public page where many customers can share ideas and will see each other's comments, and there will be a private area where concrete problems and private communication will take place.

While looking into the portal.properties I see the following properties



I expect that the described scenario cannot be easily configured with just these properties. It means that these properties cannot be controlled by role bases?
The group which may have public pages, has to be power users may solve the public pages problem.
But controlling the private page to be editable or not apparently cannot be differentiated. Or do we have a role based control possiblity?

What about your recommendation. From user's point of view, makes sense to have modifiable private pages in case of a company website which will collaborate with scientists (bioinformatics and genetics field)?
 
Tibi Kiss
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Just another idea. If I would like to go online as soon as possible, which approach is more viable:
- at first just disable private and public pages for every user, then later when will be necessary, I can enable it
- should I enable now, then later disable. What will happen in this case, those who already have their pages, they will still be able to use that just new users or pages cannot be created?

Basically I am interested in what is happening at these transitions.
 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The properties mentioned in your post is for user community pages. In liferay communities are the core site. each user may have their own community private or public pages.

You already have a default community that ships with the liferay tomcat bundle. You can have the company pages and anonymous pages there using permissions.
Liferay enables adding permissions based on roles to pages. when you add a page, you can add permissions using the dockbar: Manage>Pages select the page and then select the permissions

When a user is created you can decide to create a community for them, in turn creating a private page and public page. you probably want the private and public pages to have specific content, that is where you will find another property that specifies the portlet and what columns in the layout they are placed in.

To have some users have private pages, and others have public pages, will mean that you have to seperate between users somehow. That will mean that you will have to give different users different roles.

The rest comes down to communities and pages and how you display the pages in a menu in your themes. you can have the user login land you on a specific community page. This will require ext project where you will edit the post login actions and user creation of pages when signing up/logging in. ( search for the class names that are considered post login in portal.properties.)

you should also check the "Settings" in the portal section of the control panel. that will add default associations for the users (roles and communities) when they sign up. With the complex distinctions of users you will definitely need to extend liferay code in an ext project.

Try though, as much as possible to have the pages available as part of the default community and give permissions to it, and make them appear in the navigation menu based on level. It will help alot.


As for your follow up post, I suggest you'd have the default to enable the creation of the private/public pages. it will be a pain to recreate for existing users, whilst if you create and not make any links in navigation menu or dock bar, it would be much easier.

HTH


 
Tibi Kiss
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you Ali for the detailed description.

Amro Ali wrote:
As for your follow up post, I suggest you'd have the default to enable the creation of the private/public pages. it will be a pain to recreate for existing users, whilst if you create and not make any links in navigation menu or dock bar, it would be much easier.


That is the reason which I would figure out completely opposite. So thank for pointing out of this.

How the big picture it looks like now (yestarday I passed all the developer test on the new site based on Liferay), the menu on default community is already fully occupied, all the administrative (intranet like) features I'll put inside an organizational community, just because there I have space for more menu items and within that, I'll use multiple menu items with different roles.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi..please can help me ?..how disable default liferay "welcome" page for users public/private pages? ..i created a default user grup with public and private pages wich is asociated with new users accounts , but when a new user create an account he still view default 'welcome' liferay page...i use liferay 6.1 GA 2...thank you
 
grapes are vegan food pellets. Eat this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic