For the most part, my upgrade from version 4.0.2 to 4.3.5 went pretty well.  The only thing that is tripping me up is this new file system.  All of the portals I am working with right now (42 total) require that all of the files located within them be publically available. 

I am trying to figure out the details on how the folders have been protected during the upgrade.  I do not want to give the "All Users" role view permissions for every folder, but for the time being this has been my only work-around.  I have a lot a folders, so that took all day and night yesterday for one portal.  The others cannot be upgraded until I am able to better understand this secure file system feature.


I took a look at the folders table this morning and it appears that all folders except the root are set to "false" in the "IsProtected" field.  However, all of the folders were indeed protected, as the files were not available to the documents module or via links either.  When I assign the "All Users" role permission to view and then recycle the Application Pool, the files in those folders become available again.

My initial question is, "What is this 'IsProtected' field for if it is not set to 'true'?"

I have a follow up!  :)  What actually protects the folders if this field is not doing it?

---

Will Strohl

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

Does anyone know anything about the IsProtected field and how it's used?

---

Will Strohl

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

David,

I don't think it is of great help to unbury threads from past century (or 2 years ago). In fact, for new portals the admin has to set permissions when he creates folders. AFAIK view permission is granted to root folder by default and inherited from child folders as well, but any other setting requires manual action. Most of my clients did not have any issue of adjusting permissions for each folder when upgrading. This change has been introduced with DNN 3.3.x /4.3.x about 2 years ago and I do not remember getting complaints about this item (there have been more severe problems the first version). And still do me a favour and disable the scheduled file sync job in Host :: Scheduler, use autosync in Host Settings instead to avoid data loss. thank you.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN