I've just upgraded from 4.0 to 4.3.  The problem I have run into is that the folders under the portal root cannot be accessed from the file manager (through both Admin and Host accounts).  Also, users who previously had access to download files (say from the documents module) now get a message page simply saying they do not have permission to access the file.  Even as the Admin user I'm locked out.

The page generated simply says "You Do Not Have Permission To View The Requested File".  The HTML source is just that.  No tags or anything just the text.

To add to this, when oone tries to upload a file in the documents module, the upload works without problem.  And, user can access the file as usual through the module.  So this only affects files that are already uploaded.  But, when one does uplad a new file, all of the directories listed in the File Location list box all have "//" after the name.

This issues does not seem to affect the repository modules and files.  Only the Documents module.

Any thoughts or suggestions?

It's the 4.3.3 version, the latest that's on the site now (sorry I did not specify).

All of the permissions were previously set and users could, and have been, accessing the files without problem.  This permissions issue only started after the upgrade.

Like I said though, even as the Admin I cannot access the files.  I understand your linkclick.aspx angle but it still would not explain why all the subdirectories of the portal root are not showing in the file manager.  I cannot see any of the other folders under the portal root.  Just the files.

anthony.glenwright wrote
Do you have file permissions set so that all users can view the files you are exposing through the documents module?

Hmm...

That question is rather presumptuous.  File permissions? Where?  Is this a setting in the "Documents" module, or the File Manager? is this a setting in the Host panel or Admin panel? NTFS? Care to specify? Are you suggesting that all users should have 'View Folder' permissions on the 'File Manager', 'Security Settings' page?  If so...then why doesn't version 4.3.3 upgrade just set that by default? (To preserve the previous behaviour?)

I think the more relevant question is: "Why/How does version 4.3.3 alter the file permissions from their previous settings?"  For example, I was running a fresh install of 4.0.3 then applied the 4.3.3 Upgrade package.  What was working is now not working and I am having a difficult time understanding:

1. what has changed so that first my users were seeing a 'Permissions not sufficient' message and now (after I've applied the latest Documents Module update) only administrators can actually view the list of documents in a document module instance.  (For all other users the table appears empty)
2. what to change to restore the previous behaviour.  (To ensure that visitors of my site are able to download the same files they were able to download prior to applying version 4.3.3).
3. why does version 4.3.3 alter the permission settings? why did nobody mention it?  (I'm looking in the DotNetNuke_4.3.3_Upgrade.zip package -- there's nothing in the Readme.txt which might indicate that file permissions are to be altered by this upgrade).

I've looked in the "Help" and "Online Help" for both the Documents module and the File Manager module and I see nothing that would indicate that (a) file permissions must be set one way or other to allow anonymous visitors to view the files; or (b) the Documents module has undergone a breaking change in this update.

I've looked at the new drop-down list in the File Manager:

• Insecure - File System
• Secure - File System
• Secure - Database

Is that somehow related to this whole problem? WOW! I hope not...That new drop-down list is so under-documented that I'm afraid to touch it! It's currently set at "Insecure - File System" -- so should I assume that anonymous visitors to my site should be able to access files within the folders of my site? I hope so because there are images, documents, css files, you know...stuff that I want people to see or browsers to download.

If I change it to "Secure - File System" will DotNetNuke then require an SSL connection or enforce authentication before displaying any content within those folders?  Forgive me if this sounds like a ridiculous question but without any documentation about the behaviour of this feature...well...I'm left guessing.

Running Blind.