Overview
This training article aims to provide information on the File Management feature for DNN and how assets are managed on the DNN environment. This article is also intended to train agents on how to handle tickets regarding File Management.
L1 Agents
30 Minutes
Prerequisites
- Completion of the Third-Party Component Integration course
- Have a DNN Test environment.
- Be familiar with file extensions and uploads.
Introduction
What is Digital Asset Management (DAM)?
DNN customers widely use the File Management feature (Digital Asset Management is also known as DAM). In DNN, the DAM feature is used to administer existing files or upload new files from your local computer to the website.
History of the DAM module
The DAM module has been included in the DNN application since its conception, but the module has evolved into different variations as newer versions of DNN were released. We will cover how both versions function later in the course.
Until Evoq 8.5, the Digital Asset Management module was part of the Admin and Host menu utilizing Telerik Treeview menu controls.
Digital Asset Management Menu Pre-Evoq 9
In Evoq 9, the DAM module was deprecated and replaced by the Assets menu in the Persona Bar which now can be accessed via the Persona Bar (Content > Assets) with a complete reworked UI.
Digital Asset Management Menu Evoq 9
Description
Basics on how to utilize the DAM features
The DAM module is widely used for its three main features:
File upload
The DAM module has an upload feature that allows users to upload images, documents and videos to the DNN environment. Below is a map on how to access this between the pre and post Evoq 9 versions.
| Pre Evoq 9 | Admin/Host > File Management > Actions > Upload Files |
| Evoq 9+ | Content > Assets > Add Asset |
File upload for Evoq 9
When a file is uploaded to the DNN environment, it first checks a list of allowable file extensions as a form of security to prevent unwanted files from being uploaded. You will need to check Security > More > More Security Settings > Allowable File Extensions. For example, if you wanted to upload an mp4 video file extension, you would need to append "mp4" separated with a comma, and this would tell the application that it is okay to accept these file extensions for upload.
Folder creation
| Pre Evoq 9 | Admin/Host > File Management > Actions > Create Folder |
| Evoq 9+ | Content > Assets > Create Folder |
Permission-based security and workflow-based security
| Pre Evoq 9 | Admin/Host > File Management > Right click specific folder > View properties |
| Evoq 9+ | Content > Assets > Edit specific folder |
To cover Permission-based security and workflow-based security in detail, you will need to review the Edit Folder Permissions and Editing Workflows
Common Usage
Known issues with the DAM module
I cannot upload a pdf file, but images can be uploaded
The reason why this occurs is that there is a security setting called "Allowable File Extensions" whose sole purpose is to prevent unknown file extensions from being uploaded into the DNN environment by DNN users. The solution would be to append the file extensions that were being blocked into the Allowable File Extensions list.
A folder/file is missing and not displaying on the DNN File Manager; however, the folder/file is present on the file structure.
The reason why this occurs was described above; either the user has uploaded a file directly into the DNN's file structure, or the file synchronization has not executed to populate the database with the folder/file entries. The solution is to manually trigger the file synchronization through the "Sync this folder and subfolders" button.
I am unable to find the upload button in the Editor for some of my users but I am able to upload as a superuser.
The reason why this occurs is due to a permission setting in the Editor. You will need to manually enable this in the CKEditor settings whenever a custom role has been created on the website and append the appropriate permission accordingly.
The DAM module is not available in Evoq 9+, how can I make the module function again?
The reason why this occurs is that in version Evoq 9, we completely moved away from Telerik and deprecated some DNN API methods. Since the DAM module utilizes the Telerik treeview feature, this module is known to produce errors in an Evoq 9+ environment. The solution for this issue is to upload an updated version of this module and upload a dll file that allows the Telerik references to be used.
Comments
0 comments
Please sign in to leave a comment.