anthony.glenwright wrote

In file manager.  If you read 'joliver8's post, to which I was replying, he already mentioned the file manager.  

That was not obvious. Apparently, joliver8 is also confused about this issue (as he's been busy in these forums to discover the cause of the problem).

anthony.glenwright wrote
No, on the folder(s) in question.  The permissions are down the bottom of the file manager page.

That was also not obvious. And...my point was that there was nothing in the DNN release package which would indicate that I'd have to make any alterations to that configuration.  Furthermore...it appears that the File Manager is not quite operational yet as there is a new "Recursive" checkbox which must be turned on so that the folder-tree works as it used to -- not to mention that there are new 'empty' folders under every node in the folder tree.  (If these are supposed to be there...then it would sure be nice to have had some documentation about it).

anthony.glenwright wrote
Section 7 of the readme for the documents module states: "The documents module implements the new core secure storage feature.  File security can be controlled in the File Manager page in DNN.  Only those files  that the current user has access to will be shown by the documents module."

But it wasn't the Documents module which caused the problem! My point is that when I upgraded the DNN core, suddenly all the Documents module instances were broken.

To note:  I've fixed the problem by:

1. After updating the DNN core to 4.3.3, I installed the latest Documents module.
2. Then I visited the 'File Manager' and clicked 'Recursive' checkbox then navigated to the Portal Root folder and gave 'All Users' 'View Folder' permission.
3. Then I navigated to the subfolders which I've been using for documents and archives and gave 'View Folder' permissions.  (I tried very hard to ignore the empty folders under each node -- good thing too because I can't actually navigate to those folders or alter their properties or remove them or rename them -- why are they there?)
4. Then I navigated to EACH AND EVERY Documents module instance throughout the portal and clicked on EACH AND EVERY document to edit their properties.  When editing their properties I discovered that EACH AND EVERY document needed to be re-mapped...because:
   1. The document *should* exist in (for example):
      1. a folder called "Archive/" (Which I had given 'View Folder' permission)
   2. But it was (for some unknown reason):
      1. in a folder called "Archive//" (Which evidently I cannot give 'View Folder' permission...and this path actually doesn't exist)
   3. So I had to ensure that all the documents were properly mapped to the right folder.
5. When I had changed EACH AND EVERY docoument, it all appears to be working.

But I'm still very confused by the "File Location" drop-down list:

• Root
• Archive/
• Archive// ?
• Containers/
• Containers// ?
• Skin/
• Skins//
• UltraPhotoGallery/
• UltraPhotoGallery//
• etc.

All of my Documents have always been in the "Archive/" folder.  But after the Core update, the documents were (somehow, for some reason) in the "Archive//" folder which doesn't (and shouldn't) exist.

Still running blind.