Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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 ...Including Current Web Site Into DNN?Including Current Web Site Into DNN?
Previous
 
Next
New Post
6/23/2006 5:48 PM
 

We currently have 2 intranets that were getting ready to incorporate into 1 site.

I looked at DNN as possibly being the foundation of the new web site since it already includes all the security and modules that the company can use to keep the employees uptodate on events, Announcements, etc. This way im not reinventing the wheel.

After playing around w/ this basic functionality for a few days i have come to the conclusion that this would work very well for the foundation for the rebuild of our intranets.

Here is where im confussed as to how to implement DNN as the foundation but include all the web applications that we currently have up and running.

For example i have an application that the Quality department uses to track our defacts per work order. This application gives the user the ability to create, update, and print the data as needed. Most all the applications center around this type of layout w/ the exception of some that are a little more complex.

I guess my confussion is how to implement these existing applictions into DNN.

Should i create modules for all the applications? (Which does not make sense because the module would only be useful to 1 page and 1 application)

Or do i just create a new directory on the existing webSite called, umm Departments, and then for each department (quality, accounting, HR, etc.) create a new directory where i will add all my pages for each application? (this is how the current web site is set up. I have 1 main folder and in this main folder i have a directory for all the departments and then all the applications live in the associating demartments folder)

I created a directory /Departments/Quality/Default.aspx.

I added code on the page to display the email address of the current user logged on. Then i set one of the links in the menu to point to that page but when i try to browse to that page i get a directory listing denied.

Any ideas on this?

Any information that you guys could give me would be great.

 
New Post
6/23/2006 7:34 PM
 
To start just create you pages and use the Iframe to being in the functionality of the existing web sites.  Then you can rewrite the applications to be module(s).  Modules are not limited to only having one screen, you can create modules that have multiple pages / steps.  You can also have modules on the same page communicate toghet using the Innermodule Communication Features.  Check out the tutorials by Micheal Washignton and the DNN book written my some of the core team members Professional DotNetNuke 4.0
 
New Post
6/23/2006 8:44 PM
 

So are you saying that i should create modules for everything ?

If i use the IFrame and display what i currently have for now, is there a preferred way to extend the login capabilities to the old site?

Do you know of any tutorials or articles that talk about creating dynamic input forms?

 
New Post
7/4/2006 11:49 AM
 
lmf232s wrote

So are you saying that i should create modules for everything ?

If i use the IFrame and display what i currently have for now, is there a preferred way to extend the login capabilities to the old site?

Do you know of any tutorials or articles that talk about creating dynamic input forms?



1) Yes, create module(s) to replace the old site functionality to DNN.  Iframes are just a temporary solution while you get the time to migrate the functionality to DNN modules.

2) Not sure how you would so this and I have not seen any tutorials on this.  Unitl you migrate the functionality to DNN modules your users just might need to login manually to the sites you are accessing through Iframes.

3) Do a search for DotNetNuke Form modules.  There are a number of modules that allow you to create forms for you user to enter information into.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Including Current Web Site Into DNN?Including Current Web Site Into DNN?


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out