Liferay can't edit folder permissions in a particular site - liferay

I am struggling with a weird problem. I can't change folder permissions on folders inside a particular site. When I click the edit permissions link on the folders the modal window shows up empty. I am logged in with a user with the Administrator role. The same problem happens with web content and document library folders.
I am running Liferay Portal Enterprise Edition 6.2.10 EE GA1.
Best regards,
Fabrício Sperandio

Related

IIS website needing permissions to modify own folder

I have a website I am setting up which creates a subfolder to its own location based on which user logs into the website. An administrative account we'll call admin runs the website through IIS Manager (as indicated through the basic and advanced settings on the site's tab in IIS, which indicate the credentials for admin are correct), and admin also has full security permissions to the folder that IIS refers to. The website is I think otherwise fully up and running because the login screen loads successfully. However, despite the fact that admin is both running the site and has full access to the folder, it is failing to create the folder and as such is failing to operate the website properly. I know it is this error because the website's error logging reports an UnauthorizedAccessException to the folder I would expect to be created.
Can anyone help me figure out why it is unable to create a folder in the website location? Thank you.
To fix issue, you can try to add the IIS AppPool user to the root folder of your application by right clicking the folder and selecting Properties. Select the Security tab and add the IIS AppPool<AppPoolName> user.
And you can also decide to create a custom user to access the file system from IIS. Create a new Windows (or AD) user and click your site inside the IIS Manager. From the Actions window click Basic Settings. Finally, click the Connect as button and input the new user below Specific user:

Liferay document checkout/in permission

I am using Liferay 6.2 EE sp7 Tomcat bundle on Linux.
We have a use case for the normal regular users to upload, check in and out documents from the document and media portlet.
I see the Checkout and Check in options when I am logged in as a administrator but not as a regular user who is a site member with default permissions.
Question:
Is there a way to turn on the Check out/in options for the regular users either with configuration via properties file or permssions etc.?
Steps I took:
As an administrator:
Create a site with private pages only.
create a private page and add document and media portlet and a document and media display portlet to the page.
create a folder in the site.
upload couple of documents to the new folder.
You will be able to see the checkout option after clicking on the document you just uploaded in either of the portlets (see screen shot)
Add a regular user(non admin) and make a site member of the private site.
In a different browser:
login as the regular user and navigate the private page/site created above.
click into the folder/file uploaded above.
the Check out option is not present.
I have researched portal properties, portlet permissions and the configuration option of the portlets above. I don't see anything that is hopeful or that works.
Please let me know if there is a work around or configuration I need to do turn this on.
Thanks a lot for the insight!
I've checked it on liferay-portal-6.2-ce-ga5, but I think it can be similar in your version. You can set this permissions for "regular user" role (I set it for Power User role):
Documents and Media Display > Document: Override Checkout
Documents and Media Display > Document: Update
"Override Checkout" permission requires "Update" permission.
After this checkout/checkin options are available for my non-admin user.

limit access to SharePoint Site

I have a site collection with a subsite. I am storing a roadmap and some other project management documents within a document library in my subsite. I would like to share that document library with an internal user, but I don’t want her to see anything else – just that document library. I don’t want her to see any other parts of the site. Can I do that? How?
Yes,
Go to Site Settings > Site Permissions
Remove the user from all groups (click on Check Permissions to see what permissions she has on your site).
Go to the document library and click on the Library tab in the
ribbon.
Click on Shared With (far to the right)
Click on ADVANCED
Click on Stop Inheriting Permissions, confirm with Ok
Click on Grant
Permissions and give the user the appropriate rights (read, edit
etc.)
EDIT:
This is for a SharePoint 2013 site. Sorry for that. I dont have a SharePoint 2010 site available right now so I cant give you the exact steps, but the concept is still the same:
Remove the users permissions to the site.
Stop inheriting permissions for the document library
Grant the user permissions to the documet library

Why can't users in the "Visitors" group access my SharePoint 2010 publishing site. It works when i promote them to the "Members" group

When I place a test AD account in the Visitors group they are unable to view any pages on my new intranet site. The users receives the "Error access denied" sharepoint screen and indicates that the account was able to authenticate, but that some authorisation rule is permitting it from viewing the page.
When i remove then and place them in the Members or Owners groups they are able to view the pages as well as perform the expected functions like editing content and creating subsites.
Interesting, while in only the Visitors group, users can view the "All Site Content" page that is located here: /_layouts/viewlsts.aspx but not /pages/default.aspx.
Has anyone experienced this before?
Environment info:
1 Web application, 1 Site collection using the Publishing Portal template. A few custom master pages, lots of custom page layouts and user controls. All deployed via features.
Sharepoint 2010 Standard edition, 64bit running on Windows Server 2008 against SqlServer 2008 Enterprise Edition. Authentication is against AD, not any other forms auth providers etc.
One likely reason for such behavior is that it tries to access a resource on a page which might not have been published to a major version. For example, if versioning was turned on on images library and an image's version is 0.1, if that image was used on version 1.0 (published) of the page, the server would deny access to the visitor and ask for credentials.
Make sure following:
At least one major version of the page exists (page was published at least once)
All resources (images, movie files etc) used on the page are published (to major version)
You can use "Draft Check" button on Page Tab of the Page's ribbon to check the unpublished resources that are used by the page.
I had the same issue and I've finaly found out how to do this:
If you check OOB group access, you can find that Visitors group has limited number of pages where it has granted access.
Navigate to /yourweb/_catalogs/masterpage. Here you'll find many
.aspx files (including default.master).
Open this default.master`s permissions and you see it inherits from
Master Page Gallery.
Click this permissions inheritance and you can see that Master Page
Gallery permissions are not inherited from site collection
permissions.
Give here the Contribute permissions to Style Resource Readers (or
modify it as you'd like) and all users will have access to this web
with no permissions to edit etc..
I had a similar issue and the thing I noted in your Environmental comments was the custom master pages. Go to your Site Settings and ensure that your custom master pages have been published. If you need to publish them also check the corresponding html pages after they have been published as they may need to be republished also.
This worked for me.

Cannot save layout page in Moss

I am trying to update a layout page in Sharepoint Designer but when I click Save I receive an Access Denied error. I can see that the layout page is created by the system account. I am in the site owners group so I think I should be able to make modifications to the page.
Any help?
The page could be checked out by the System Account or never had a published version, also, site owners have limited permissions in the site collection (where the page layouts reside)

Resources