Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...TIP: Turn OFF Journal File AttachmentsTIP: Turn OFF Journal File Attachments
New Post
6/19/2013 1:54 PM

As of DNN 7.6 the journal shows considerable promise in enabling and building a robust social community. One of its major drawbacks is that files and images uploaded  through the journal get saved in the web server Portal/Users folder. As a result a robust and active community that uploads images and files can quickly overwhelm the expensive storage capacity of hosted DNN websites and portals.

The simple fix for this is to go to your journal module instances and turn OFF "Enable File Attachments" and "Enable Photo Attachments."

There are several reasons to make file and photo attachments DISABLED. One is that the Journal files are saved in the Portal/Users folder, which cannot be successfully mapped to a cloud storage provider like Amazon S3 or Microsoft Azure. The journal uses an API that creates User folders on the fly so even if you successfully move the existing folders and content of the Portal/Users folder to the Cloud any time a new user is created and they upload a file via the Journal the API will create a new folder on your local file system and try store files on your local web server instead of the cloud. This is because the Journal API doesn't use the standard DNN file system methods for creating folders and accessing files.

Second, because the journal doesn't use the standard File System methods users cannot add new files through the journal if the Users folder is mapped using a cloud provider. User can attach files that already exist in the folder, but this requires admin intervention to get the file(s) via ftp or the DNN file manager. I don't think a DNN admin wants to upload score, hundreds or potentially thousands of files and photos for users via FTP or the DNN file manager.

Third, the journal doesn't store attached file locations using the standard LinkClick url. This means that any files that are somehow saved to the journal it will never migrate successfully to the cloud. Any time a user clicks on an image or file link the Journal will try to refer to the local copy instead of the generic LinkClick mapping which supports cloud migration. This means that even if you can allow users to add files and then find out you are running out of space, you won't be able to migrate  the existing journal to a cloud provider. The Journal will always look for the old files or photos in the local file system, so old images won't display correctly and old file links will be broken in the journal.

The file location path is saved using a physical path instead of a flexible DNN URL that uses the LinkClick method. This is somewhat odd because the HTML module uses the LinkClick method for showing the path to the file, but the Journal module does NOT use the LinkClick method, so Custom folders and files uploaded via the HTML module can migrate to the cloud without issue but the Journal files won't and/or entries cannot be migrated to the cloud without significant SQL scripting to update legacy journal photo and file paths..

DNN is a GREAT solution and the social features are pretty darn cool. It would be nice to see the journal support social features that have long been available in many social sites.

So... save yourself some grief and turn OFF File Attachments and Photo Attachments in all of your journal module instances. Someday, and hopefully in the near future, the DNN Journal and its API will support proper cloud storage integration, either natively or through existing 3rd party modules. Until then play it safe, save some money and keep your users Journal postings limited to text and links.



New Post
6/19/2013 2:23 PM
Joseph, no doubt Dotnetnuke will respond to this with a solution because it sounds serious what you write.
New Post
6/19/2013 2:36 PM


I hope they can make it happen, and quickly. In theory the solution is simple, use the File Manager API for creating folders, and use the same folder type as the Portal/Users folder.

And then use the LinkClick path in the ItemData field of the Journal table. If you want to check it you can do a query against the Journal table to see what is stored in the ItemData field.

SELECT ItemData FROM Journal

You'll see images have something that will look like this: {"ImageUrl":"/Portals/0/Users/005/05/5/facebook_icon.jpg",

 The HTML module uses image paths like this:

 Using LinkClick method to specify the image path allow for the path to be changed to the cloud via a provider without having to make big database changes.



HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...TIP: Turn OFF Journal File AttachmentsTIP: Turn OFF Journal File Attachments

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

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

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?