I am new to using Liferay, and practicing currently on Liferay DXP. I have created various user, and wanted to add different content to dashboard of any user. Such as asset publisher which will list all the assets published by that user. I am able to add this modified content only for Admin User. I am not able to find any setting where I can change the look and feel of dashboard for every user.
Can anyone please help me where I can find it? It might be pretty simple but I am unable to find it.
Thank you in advance for helping me.
You can look at the ADT. Modify the templates as per requirement and on user roles. You won't be able to deliver content as per individual user but to roles. You can also have portlet preferences to show different content on different criteria. This all is possible. You will have to study the subject more. It will be very difficult to detail out the whole stuff here. But yes with ADT in Liferay 7 / DXP you have a lot of flexibility.
Related
I'm using liferay-portal-6.2-ce-ga5 in which some functionality like assigning a site to a new user or giving to use social office etc. So we can see here admin is assigning a site so what I want that it should be done automatically or any code so that it can be achieved?
If you're doing it to everybody (e.g. every new user should be member of a specific site or have the same role, like "Social Office User"): Go to "ControlPanel / Configuration / Portal Settings / Users / Default User Associations" and configure as you like.
If this is not what you're asking for, please rephrase your question to be more specific.
For programmatically achieving this, you'll find a bunch of sample code in James Falkner's blog article on the ancient sevencogs code.
First of all, let me tell you what I am or my company is intended to do. We have already developed a project using Java, JSP and Servlet. We want it to integrate with Liferay so that we can change logo, css, images, themes or any other UI related component at run time using Liferay admin panel. But backend should be what we have developed.
In short, the UI of our project is controlled by Liferay, but control of data displayed on UI or submitted from UI should be from our developed backend code.
Now I have a few questions regarding above said approach of fulfilling the requirement:
What we are trying to do is possible?
Is this approach recommendable for what we intended to do?
Or do we need to develop our project from scratch to fit into Liferay? Like developing portlets and deploying in Liferay or other approach that has been given in Liferay documentation.
What about database integration? We have around 15 columns/fields in user table in database of our project which is completely different from that of Liferay's user table.
Liferay is a very new for us. We have checked the documentation section of Liferay but still few things like above said requirements and its implementation is not clear. Also, we would like to know in what scenarios/requirements Liferay is useful.
Ok let me try to answer your question point-wise and I would answer your last question first, which should automatically clear other questions:
Q. Also, we would like to know in what scenarios/requirements Liferay is useful.
This can have a very wide answer, but I have made it shorter for you:
If your site is content heavy and not data heavy then go for Portal
If you plan to use only a single web-application in a portal then I would suggest standalone custom developed web-application is much better.
I agree liferay portal will give you lot of things out-of-box like Single Sign-on, authorization, authentication, friendly-url and page creation and also lot of applications like Blogs, Wikis, Document library, some social networking apps etc. But think about it, do you really need all this? if not, then this is overkill
Here are some really nice links to better understand a portal's usage:
When to use a portal
Why to use portal technology
liferay tag wiki: It has nice description as to what is liferay and it also contains relevant links to Admin guide which will tell you what all functionalities liferay has and how you can manage it.
So still if you find your other questions unanswered, read-on ...
Q1. What we are trying to do is possible?
Nope. Portlet technology is different from Servlet technology. Liferay (or anyother portal) does not provide a way (atleast a simple one) to integrate servlets that would render pages inside a portal. For eg: Since with servlet you define URL mappings for a particular servlets before-hand in a web.xml but in a portal the URLs are generated by the Portlet Container. So portals work with portlets and not Servlets.
Q2. Is this approach recommendable for what we intended to do?
Nope. As I already explained in Q1.
Q3. Or do we need to develop our project from scratch to fit into Liferay? Like developing portlets and deploying in Liferay or other approach that has been given in Liferay documentation.
If you want to go the liferay way then Yes.
If you want to build applications that talk to your custom tables then portlets are the way to go.
Q4. What about database integration? We have around 15 columns/fields in user table in database of our project which is completely different from that of Liferay's user table.
If you go with Liferay. In this scenario you can create a combination of liferay-hook & portlet (may be using service-builder) to customize liferay's User creation mechanism and there by store data in both Liferay's User table and your custom tables.
Liferay's permission system is really fine-grained so you can also benefit from this system and put permission even on the data level.
In conclusion I would say:
Everything boils down to what your requirements are and what resources you have. And sometimes what future requirements you can have.
Note: All the terms used in this answer which are specific to liferay (like service-builder, hook etc) are explained in the liferay tag wiki.
Hope this helps. If you would like to know anything specific I would gladly update my answer.
Hi I am little new to SharePoint. Here is my question
How can we make different views for administrator VS logged in user. For instance I need to display the
quicklaunch only to admin and not for user. And user should not see site actions tab.
How can we set this. Please can anyone come up with solution or any blog that we can refer?
Thanks in advance.
This blog will help with code identifying whether a user is an admin (or even just owner) http://blogs.tamtam.nl/duarte/2008/12/09/Sharepoint+How+To+Verify+If+A+User+Is+Site+Administrator.aspx
You can then create a control that uses this condition to display or hide content. See my blog here for an example: http://jcapka.blogspot.com/2009/02/handy-hiding-panel.html
You can also use the built in SPSecurityTrimmedControl but it does not provide a means of explicitly checking if a user is an administrator.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.spsecuritytrimmedcontrol.aspx
I have modified my MOSS 2007 configuration to query a given target AD successfully. I would like to show some custom LDAP fields (such as country) in the PeopleEditor control and allow users to search against these fields. Can someone point me towards useful resources/tutorials showing how to do this?
Thanks, MagicAndi.
You need to inherit from the EntityEditor control (just as PeopleEditor does) and write your own queries and validation.
Some background (read community content):
EntityEditorWithPicker
PickerDialog
SimpleQueryControl
Along with these links and carefully studying the PeopleEditor control with Reflector, another good resource is this blog post from Igor Kozlov. There's a less detailed but still useful example on MSDN here.
I'm working on a CodePlex project that queries any given Active Directory from a people picker. It's well documented and combines techniques from the various references out on the web (giving credit of course). Hope it helps someone as well!
A first step should be to map the fields form the AD to a attribute in the SharePoint user profile. You can do this in the configuration of the Share Service Provider (Central Administration > Shared Services > User Profiles and Properties).
There you add a new attribute and define which AD field should be mapped to it. You can also define which fields the users are allowed to override (but only in SharePoint, it's only a one ways synchronization) and which one are read only.
This blog post shows how to configure the SharePoint search to be able to search users by a custom attribute in the user profile.
I hope this will point you into the right direction.
We have a doc library, Requirement is that only the user who has contributed to the document should be able to see the document and other user who has access to the library should not see that.
Can you please help me to achieve this.
Update: I talked to my TL he said, we need multiple Views on the Doc Library. Any one with new Ideas?
Add a custom view to the document library that only displays the items if the current user == creator of the document.
Set this view as the default view.
Prohibit users from changing the view.
If you are after a true permission based solution, you could develop a event handler for the adding item handler that sets the permission on the newly created item.
(By breaking parent inheritance also)
Set only permissions (owner) for the user that created the item.
EDIT: Just re-read your question. I didn't understand correctly. I missed the "contribution" part. Anyway, I will let my answer be here.
Adding a view is not really good practice. If one want's to gain access to the data he can do so by working with the lists web service. the solution is much simpler then it seems.
1. you need to install this: http://spdactivities.codeplex.com/.
This add-on will add you work flow activities to the SP Designer.
2. create a workflow doing what you described. It will take you no more then 10 minutes.
That's it :)