Tag Info

New answers tagged

0

We need to check the user login or anoymous access, then check the permission: SPUser currentUser = SPContext.Current.Web.CurrentUser; if( currentUser != null && !string.IsNullOrEmpty(currentUser.LoginName) { bool permit = item.DoesUserHavePermissions(currentUser,SPBasePermissions.Open); }


3

If you enable anonymous access to your site (or parts of it), you still need to deactivate “Limited-access user permission lockdown mode” Site Collection Feature if you want those users to be able to dive into Lists or Libraries. Enable anonymous access in “Authentication Providers” (Central Administration > Application Management) Grant rights to ...


0

This is very much common error now days which occur when you ignore the Object Cache Settings. So Please Configure the Object Cache settings for that web App. Create the Super User and Super Reader Account Add Both account into Policy for web app, Super Reader as Full read and Super User as Full control Now run the below power shell to add the user: $wa = ...



Top 50 recent answers are included