You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Permissions work at a top-level folder only and it makes assumptions from there. The route manager should be able to dissect which file is attempting to render and check specific permissions. Some files such as .html files may not exist and if that is the case the permission system should fall-back to the current folder
The text was updated successfully, but these errors were encountered:
Currently if a standard user tries to access a folder in DNN that will be denied unless it is explicitly added. In my testing copying a static html website inside of a portal doesn't automatically add it to the folder table in DNN. This means that all users won't be able to access the file.
I think we can add a workaround where you manually add the row to the Folder table and apply the permissions by hand. This isn't a very good feature and needs a better configuration story
Copy static html files over to desired location. In my example I created a team wiki in portal 0. ~/Portal/0/Wiki/index.html is the root page
Log in to DNN as super user
Go to Manage -> Site Assets
Right-Click on Root and add a new folder called Wiki which matches the folder already created
Select Standard Folder
Once folder is created there will most likely be nothing showing up from the DNN user interface, which is normal. Right click on the folder and select view folder properties
Navigate to permissions and add your role or user to access Browse and Open permissions
This is working as designed according to DNN specifications. We need to add better documentation around this story. I am updating this work item to a documentation item and it is not a bug
The Permissions work at a top-level folder only and it makes assumptions from there. The route manager should be able to dissect which file is attempting to render and check specific permissions. Some files such as
.html
files may not exist and if that is the case the permission system should fall-back to the current folderThe text was updated successfully, but these errors were encountered: