Understanding DNN on existing website - dotnetnuke

I started working on an existing website that uses DNN. I am having difficulty understanding and accessing DNN in their staging/test environment. In IIS there are a few different websites. How can I figure out how to get to the main Admin DNN screen by looking at the information in IIS and exploring to files. Once there I need to apply new licenses for DNN.
Thanks in advance for any assistance.

In IIS, right click on the website and choose the Manage Bindings option, that will show you the various Host Names (URLS) that are configured.
Try those URLs, and then put ?CTL=login on the end of the URL to get DNN to load the login control. From there you can login with a HOST or ADMIN account, HOST/SuperUser account would be best, as you can then go to the Host/Portals (Site Management?) page and see how many different "sites" are configured within the DNN installation.

Related

Can't access wp-admin after migrating website to Chinese server

Hello I'm having some issues with accessing my wp-admin after migrating a website onto a Chinese server.
I used WP Migrate DB plugin to ensure all mentions of my old domain was replaced with the new domain.
I deactivated plugins, changed the theme, created a new admin user, checked user roles and a few other possible solutions that I can't recall at this time.
Looking for general ideas on how to resolve this that I might not have tried.
Thanks

Access dotnetnuke site

A very nooby question here, but I do need to ask...
I have been passed a dotnetnuke site, created around 2010, all I have access to is the FTP for the hosting space, so I can see all the files. What I need is to find where the site keeps it's admin panel, so I can manage the pages. From what I have seen online, I need to go to mydomain/dotnetnuke, but there is no such subdir on my host, I suppose the old version I am running probably had a different convention.
What are the older defaults for DNN, from around 2010-2011 (community edition)?
thanks
You can get the login screen by putting ?ctl=login on the end of the url to the website. You will need the admin account info though to login.
The database will have the username and password, but the password will be encrypted.

Disabling website to everyone except portal administrators or host users in DotNetNuke 7?

Is it possible to disable a DNN portal, or an entire DNN installation to everyone except administrator / host users?
I need to update a DNN website and apply new themes to differant sections of the website, however this will take some time on the live website.
I'd like to achieve similar to this "Wordpress Maintenance Mode" module plugin.
I'm aware of using the APP_OFFLINE.html file to disable the entire website, however we need a couple of admins to go in and make changes whilst keeping everyone else off the website.
There isn't a maintenance mode in DNN. What I would do is the following.
Setup a new website in IIS, beta.mywebsite.com. Have that website point to your Existing DNN folder.
Point your current website to a new folder with the App_Offline.htm file/message in place. Then have your admins go to the beta.mywebsite.com URL instead of going to the www version of the URL.
That would probably be the most straightforward way to do this for DNN without writing a custom maintenance mode module for DNN.

Create DNN user from console / windows application

My requirement might be very basic, but i'm new to DNN technology. google search doesn't help me.
I have millions of users in sql server with all details like password firstname, lastname, ....
I just want to move these users to DNN database. What is the best way for that ? It can be any stored procedure calling or I can write console application for that.
I created console application, but it is saying nullreference error, as it is a console application and unable to read site configuration, is there a way to manually set the configurations?
I am using latest version of DNN software and .NET 4.0. c#
aspx page option:
Create a new page in root of dnn that inherints from dotnetnuke.framework.pagebase and use this dnn wiki page to see how you can easily create user and add it to specific role.
Windows/console application option:
You can look at http://iweb.adefwebserver.com/ which is a windows application and consuming dnn api with some web services to get data from dnn. That will be a good starting point.

DNN / WebMatrix / Localhost / Multiple Sites

It seems that DNN is undergoing an upgrade and I cannot access the forums or many of the docs. Needing an answer soon, and Google providing too many varied types of hits (none of which are helpful or most of which post to the DNN site that is undergoing that upgrade), I had a few questions about setting up DNN.
First, I am coming from Orchard. There I was able to use Webmatrix - I downloaded the web version, opened as administrator, created modules, messed with themes, etc. Using the Orchard Docs, I was able to set up a multi-tenant site and run it on local host (IIS express through Webmatrix) - this included modifying the host/config files to view the multi-tenant sites. I could then publish to my own server running IIS 7. On the server I set up the landlord site then bound the tenants with no problem.
Being new to DNN (and things not being readily available at the moment on their site), I was hoping I could get some guidance on how to set up DNN similar to what I did with Orchard.
First question is obviously whether or not that is possible (i.e., no IIS, only IIS Express (Webmatrix) on my local machine).
Here would be my other questions:
If I can run it locally, can I just download the 7.1.0 new install package, and open Webmatrix (as Admin) on the folder I unzipped it in?
Assuming I just "Run" the website, I will then set up the "Landlord" instance of DNN on the following screens, correct? (i.e., where it asks for credentials and what DB setup I can use)
Can I then go ahead and create sub-tenant sites (alias/portal)? If so, do I go about manually updating my host/config files to run those tenants (depending on the port)?
Assume all of the above is correct, do I have to "reinstall" the 7.1.0 package on my webserver, or will a simple publish from Webmatrix do (with the proper credentials in Settings)? If so, I can handle pointing to the landlord on my server and then binding my subtenants in IIS.
Sorry for the n00b questions. Thanks!
On the Download page on dnnsoftware.com, there's a link to click which will start the install process within WebMatrix: http://www.microsoft.com/web/gallery/install.aspx?appsxml=www.microsoft.com%2fweb%2fwebpi%2f2.0%2fWebApplicationList.xml&appid=106
When you create a new portal, you can specify that it uses a URL which is a subdirectory of the current URL (i.e. a child portal alias), so that you don't have to use different ports. I'm not especially familiar with IIS Express, so I would expect that you could point multiple ports to the site, and map those as different portal aliases, but not sure exactly how you could do that, if you don't want to make use of child portal aliases.
To publish a site, you should just need to push the file system and database, and setup IIS.

Resources