• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 998
  • Last Modified:

working with DotNetNuke

Hello I have acquired a website that is driven by dotnetnuke and know little about this framework. I have two major questions to ask

1. I notice that the website I am working with that is driven by this dotnetnuke framework creates directories on the fly without them being a physical directory on the server.  I was wondering where does dotnetnuke store these dynamic directories on the server or how do you configure them (i.e. change the name of these directores, location they will be written to, etc...).  Also how does virtual directories work with dotnetnuke how is it possible to have a directory made on the fly that does not have a physical location on the server?

2. How do you work with default.aspx files used in dotnetnuke.  I notice that based on the context of the page default.aspx does different things and when I go to edit page through the web portal I see the exact same thing just some html and java and know their has to be more that is being parsed by the microsoft server or something.  

3.  When dotnetnuke is installed on a server and a website build from it is the developer forced to make changes to the website through the admin area on the site or is their ways to upload directly via ftp some html, aspx, etc...  I notice that the whole site is driven by dotnetnuke and so wonder if the developer who intertwined the website in this technology is locked into making revisions basically through the admin portal and not simply uploading to the server via ftp to change or add pages, etc...

4. Is it possible to integrate java applets within the dotnetnuke framework.  Any other ideas you may have for further research on how to use this framework as a newbie to it and an administrator inheriting it from another company thanks.

1 Solution
1.  If you are talking about the "virtual directories" that are displayed in the URL of your browser, those are called "Friendly" URLs that DNN creates so that pages are indexed better by the search engines.  Without these URLs all pages in a DNN site would be Default.aspx?TabID=5, with 5 being the index of the page you are accessing.

2.  DNN only has one physical page called Default.aspx.  It is responsible for dynamically loading the User Controls (DNN Modules) based on database settings for that particular page.  DNN loads the skin file to this page.

3.  All content is stored in the database.  The only files that you could FTP to the server to change would be the Skin files, not the actual content.  DNN was designed to make it possible for non-technical people to be able to manage their sites without having to know anything about HTML, FTP, etc.

4.  Your best bet is to visit www.dotnetnuke.com


Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now