After upgrade to 3.3.5 can link a file when logged in as Host but when logged out browser window at URL http://it-ds1/LinkClick.aspx?fileticket=UEb909kvvFE%3d&tabid=192&mid=885 presents this error -

"You Do Not Have Permission To View The Requested File"

Noticed some responses on this thread suggest changing folder permissions. Changed permissions at the root DotnetNuke folder to give Everone Read & Execute permissions. No help.

Cannot find LinkClick.aspx anywhere on my web server and it seems asinine anyway to have to set folder permissions like this.

This is aother Show Stopper for the City of Wilmington and would really appreciate some help or at least some communication from the DotNetNuke community on what is being done to solve all these type bugs in this release

Thanks

 

Since DotNetNuke 3.0 there has been a concept of "Folder Permissions". These are not the folder permissions on your physical hard drive - but rather role permissions attached to the logical folders managed by DotNetNuke for uploading files. Although this folder permission feature existed in DNN 3.0, it was not always enforced conistently throughout. In DNN 3.3/4.3, the feature was completely implemented which resulted in proper security for folders/files based on role assignments. In the Admin / File Manager, there is the ability to choose a Folder from the treeview and then scroll to the bottom of the screen to set the Read and Write permissions for the specific folder. By default when you create new Folders they are assigned Read access for All Users. However when upgrading from earlier versions, it is possible that the folder permissions were not initialized ( the upgrade script was supposed to take care of this scenario ). You will want to review your folder security assignments.

---

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com

sbwalker,

Appreciate your response and you are right. Apparently from a prior version the View permissions were not set on any folder. These were old existing folders and since this security functionality is now fully implemented maybe that's the reason for my problem.

Did find that permissions do not filter down to sub-folders and that you must set the permissions on each individual folder rather then just on the Protal Root.

Thanks a lot for your help