Now, I did some preliminary testing when planning this morning's upgrade of DNN from v4.0.2 to v4.3.5.  In this testing, I also had the modules that were not current automatically installing after the portal was upgraded.  There are a few other threads in this forum and others describing all of the issues I ran into, but not a whole lot of answers have been presented.  At least, not to my satisfaction - and apparently not to too many others either.

The upgrade to DNN 4.3.5 also upgraded the Documents Module to v3.01.05.  Initially, like most other folks, I ran into an issue of all my documents not being available to users.  As I saw the module lead help give some insight, but this would be much better if everything was laid in a step-by-step describing the "Why" and "How" of all of our current pains.

For instance, I have figured out how to make the documents appear again to my visitors, but this is NOT a solution.  This is a breaking change.  To give you a bit more insight, most of the web sites I have been doing lately have been for public schools.  Since the schools are public ALL of the documents need to be as well.  What does this mean?  I have A LOT of work ahead of me.

Let me give you an example.  In order to make the documents appear in ANY documents module I have found that I have to perform the following steps:

1. Set the permissions for a folder to allow "All Users" to view the folder. 
   
2. Navigate to the page(s) that have a Documents Module that contains links to those files.
3. Go into the settings for the documents module.
4. Perform NO updates, but still click "Update" to update the module.  (Quite perplexing, no?)
   

[EDIT= Recycling the Application Process or waiting until the cache refreshes will take care of steps 2-3]

The School District web site was the first for me to upgrade.  Seeing as how it covers the entire district, there are A LOT of pages, and an even GREATER NUMBER of Documents Modules.  So far, I have not been able to find the settings in the SQL tables that would allow this to be easier to update.  I am already looking at a long night, but I am considering rolling back the update and avoid this altogether until this is sorted out by either the Documents Project team, the Core team or both.

I was able to figure out one thing.  None of the Documents have a record in the DocumentsSettings table, but it will have a record when you update it.  However the update MUST occur AFTER the permissions are updated in order to allow the documents to be visible.

Something VERY negative that I now have to deal with is everyone who can edit a portal being able to see the folders and contents of those folders when they are performing an upload of a file.  This is an extremely discomforting thought.

Can anyone offer any additional insight to this issue?  I am terrifed to find out what the next bug is.  However, I know of one other.  I cannot see my folders in the File Manager if I am using Firefox.  That is highly unforunate since I normally only use Internet Explorer to troubleshoot what an IE user is experiencing.

---

Will Strohl

Upendo Ventures DNN experts since 2003 Official provider of the Hotcakes Commerce Cloud and SLA support

Okay...  This is indeed comical!  I have been performing the steps outlined in my previous posts.  However, I then became curious about something.  I thought to myself, "With this new secure file system, what if I uncheck the 'All Users' group? Will the downloadable documents still be there?"

I asked the question, and the answer is YES.  Ha!  The documents are still there.  I am sure that there is probably something I am missing - especially with this new secure file system that no one seems to know much about, but this did not work like it is supposed to as far as I can tell.  :)

[EDIT]
D'oh!  That was a bit premature.  Changing the permissions for the folder and then viewing the contents of the respective Documents Module is not a real-time change.  Apparently, the permission settings for the Documents Modules are cached.  Further testing revealed that managing the permissions for files does work, but you need to recycle the Application Process if you want it to be reflected immediately.  Otherwise, wait a few minutes until the cache is refreshed by DNN.  Clearing the cache in the Host Settings doesn't do anything either.

---

Will Strohl

Upendo Ventures DNN experts since 2003 Official provider of the Hotcakes Commerce Cloud and SLA support