SharePoint 2010 Foundation site Read permission list item contribute permission not working - sharepoint-2010

I've upgraded a SharePoint WSS 3.0 farm to SharePoint 2010 Foundation.
Now I got a strange problem in a web part that modifies and creates Content Library files.
The user is only allowed to modify a file if he also got Contribute/Full access on site level (might be enough to have these permission on List/Library but I haven't tried). The user already got contribute permissions on the parent folder and on the file (inherits).
Another problem on the same site but on a different Library. All users on the site can read all files in this Library but when i try to copy a file from one list to another using the following code i get access denied when OpenBinaryStream is executed.
SPFile newFile = SPContext.Current.Web.Lists["ToLibrary"].RootFolder.Files.Add(folder + "/default.aspx", oldFile.OpenBinaryStream());
Both the problems only occurs on the upgraded farm and works fine on the WSS 3.0 farm.
Does anyone have any idea what's going on?

I had a similar issue which turned out to be a setting for lists/libraries. In the Advanced Settings for a list/library, there is a section labeled "Item-Level Permissions" - this setting can be used to deny access for anyone without Full Control rights to the item. Unless there is a specific need, Read Access should be set to Read all items and Create and Edit access should be set to Create and edit all items.

I had the same issue and resolved it by going to Site Settings > Edit Permission Level > and giving the 'Contribute' permission level the ability to 'Open Items - View the source of documents with server-side file handlers'

Related

Unable to list folders when using scoped app permission for Dropbox

I'm able to successfully list folder and contents when my dropbox developer app has full access, however, when I'm using scoped access only to a specific folder, it fails.
Now when I switch to scoped access to a specific folder I'm running into errors. This request should fail since the app does not have access to the folder.
Now when I put in the right folder path, I'm still getting the same error.
For reference I'm sharing my app details
It looks like you're using the App Folder permission. This will root all your paths relative to that app folder; your app will not be able to see outside of it.
For example, if the user sees the file as "/Apps/AppFolderAccess/myfile.txt", your app will see it as "/myfile.txt". By setting your path to /Apps/AppFolderAccess, it is effectively resolving as /Apps/AppFolderAccess/Apps/AppFolderAccess - which is not found.
If your application needs to see content outside its app folder, you should select full access.
Building on top of the other answer: you need to set the application permission to access type "Full Dropbox– Access to all files and folders in a user's Dropbox."
However, note that this requires you to delete your existing app and create a new one since it is not possible to change the scope of an existing app.

I can't access or edit many folders?

Is there some easy way to permanently allow myself full access to all folders and files? I am the only user on a freshly formatted PC, and every answer I could find online seemed to be per folder and a one time solution.
An example of not being able to open a folder is the WindowsApps Folder in my D: Drive.
‪C:\Program Files\WindowsApps is a restricted folder used for the Windows Store apps. It's designed that way as a security feature to limit the access windows store apps have to your Windows OS. Not all apps on the Windows store are audited and checked to confirm their legitimacy. The folder is purposely designed to act as a little island separated from your user profile and sensitive data. You can gain ownership of it though...
You already found it by enabling show hidden items, so you can go to the folders properties > security > Advanced > Change > [enter your username] > check the box to 'Replace owner on subcontainers and objects' on the next screen. You should now have access to that folder.

Avada Wordpress theme - unable to access Branding settings

We have just commissioned a new website via a commercial designer, who has used Wordpress with Avada theme and Avada Branding. As the owner of the site with an admin login, I am unable to access some Avada settings, and in particular the settings for Avada Branding. The one setting I would like to change is that the word "Avada" is everywhere replaced by our own company name, which is confusing and silly (a bit like installing MS Word and everywhere renaming it "John", IMHO).
The Settings link for the plugin (https:///wp-admin/admin.php?page=avada-white-label-branding-settings) gives "Sorry, you are not allowed to access this page".
But it's our site and I have full access via FTP and phpMyAdmin, so how can I unlock access to Avada Branding? Any help appreciated!
Avada branding is a seperate feature/plugin what needs to be installed. otherwise you will get this error, as the directory the scripts are heading to, dont exist. The separate plugin is just an addition to avadas functionality, thats why the url is recognised, but the plugin is missing. thats why you have no permission.

Prestashop 1.7 problem to access backoffice

when I m trying to access my back office I get this message
For security reasons, you cannot connect to the back office until you have:
deleted the /install folder
Please then access this page by the new URL (e.g. http://localhost/prestashop/backoffice/)
You need to physically remove/delete `/install' folder from your installation.

Error Access denied to programmatically created folder

I Have Created document set in that document i have programmatically created an Tempfolder but when i access that folder it shows error like"Access to the path 'C:\Users\Administrator\AppData\Local\Temp\MyTempFolder' Access is denied"
please guide me.
It is correct behavior because you need administrator's rights to access that folder.
The simples solution is to run you program as Administration but I would rather change the folder, otherwise you need to elevate the rights of you app.
Furhter you can look here and here.