DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Question re: site assets - using the admin interface versus loading content on the backend - pros and cons

 5 Replies
 3 Subscribed to this topic
 40 Subscribed to this forum
Sort:
Author
Messages
Growing Member
Posts: 35
Growing Member
New Poster
New Poster
Congrats on posting!

Can someone tell me the advantages and disadvantages of using site assets to upload documents versus uploading content on the backend using File Explorer?

The content editors prefer using the backend. They only have access to certain folders with permissions applied. I'd like to respond with a comparison.

I'll need to respond to a team meeting in a few weeks and I'd like to explain best practices and why.

Thanks.

Alexis

Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Using DNN upload will provided some additional checks on file types and contents.
Veteran Member
Posts: 363
Veteran Member
4 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
New Poster
New Poster
Congrats on posting!
4 Engaged Reader
Engaged Reader
You are an engaged reader!
2 Avid Reader
Avid Reader
Avid Reader art thou!
2 Most Liked
Most Liked
Congrats, your posts are really liked!

The site assets gives you the exact URL for your assets so you can easily get this information and continue working on the content creation task; also, this feature reduces to pretty much 0% the chances of using a bad URL to call your assets.

Veteran Member
Posts: 838
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
New Poster
New Poster
Congrats on posting!

File explorer....you mean like filezilla?

In that case:

  1. Points made by Marco :-)
  2. If you use Site assets, you can create a folder type database. Links to documents in that folder are not direct urls but Linkclicks. This means you canrename a document or move it to another folder without breaking the link. Important for content hygiene / integrety.
  3.  If you use Site assets, you can create a folder type secure. That way you can store documents in a way only people with a certain role can have access. For instance project teams, HR files etc.

 

Growing Member
Posts: 35
Growing Member
New Poster
New Poster
Congrats on posting!
Thanks your input everyone. Maybe I should clarify, that some staff prefer copying and pasting their PDFs directly into the \Portals\0\PDFs. They go to the html page and then link their text to their PDFs. If there isn't a pressing issue with this, is it safe to say that it is a reasonable practice? I personally prefer using SITE ASSETS and upload. I assume one can upload multiple documents at once and / or upload a zipped file in the SITE ASSETS interface. Some staff have found it tedious, especially if they are renaming their PDFS.
I understand the folder types can be customized using site assets.
Veteran Member
Posts: 349
Veteran Member
3 Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
Reasonable I guess depends on the trust you have in those users and the source of the files. DNN will do some sanity checks on uploads for various known file based exploits that windows will just ignore.

For instance an html file could not be allowed to upload using DNN and IIS might be configure to serve static html (often the case). So using DNN you could prevent that but if the file is just put there using windows, you can't.

There are some file based hacks where serving the file could run code, DNN would prevent uploading such files with commonly known embedded hacks but windows will just let it go. You might trust the user but if the user got the file somewhere else, can you trust the file to be clean...

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved