Geek Answers Handbook

How to access the contents of the DotNetNuke portal?

General question about Nob on DotNetNuke, using it for the first time.
My client gave me a dump of his site (made in DNN), and he wants to host his site.

He has a list of portals. I would like to know how I can view it in localhost.
I created a DotNetNuke application in my local IIS that points to the code that my client gave. There is a DotNetNuke.webproj file in this folder.

Inside the Portals directory, I got, for example, a folder called StackMe. How to access this portal?

When I go to http://localhost/DotNetNuke/ , it redirects to http://localhost/DotNetNuke/Install/UnderConstruction.htm

+4
source share
3 answers

If it is redirected to Under Construction, the site may not be able to get into the database. DotNetNuke cannot display anything without connecting to a database. You can get more information if you try to click http://localhost/DotNetNuke/Install/Install.aspx?mode=none

Portal mapping by URL is processed in the PortalAlias database PortalAlias . You just need to add your localhost URL to this table, and then you can access the site (as soon as the site can get into the database). If the site has multiple portals, you need to add an alias for each portal that you want to access.

+8
source

If you see a page under construction, something is wrong (the captain is clearly here).

Some troubleshooting steps on the local computer:

  • Rotate custom errors in web.config file. Just so you can see any ASP.NET errors if they bubble up.
  • Make sure DotNetNuke can connect to your database. There are two places that you need to check in the web.config file.
    • In <connectionStrings> check the <add name="SiteSqlServer" ... /> element.
    • in <appSettings> check the element <add name="SiteSqlServer" ... /> .
  • Find the DNN tables in your SQL database. The table that interests you will be called "PortalAlias" (or "dnn_PortalAlias" or any other prefix for your table). Each portal maps to a URL. If DNN detects that you have arrived at the site using a URL that it does not recognize, it will redirect you to the one that recognizes.
    • Run the SQL query and see what's in PortalAlias ​​(run select * ). Pay attention to the portal identifier.
    • Insert a new record into the table. INSERT INTO PortalAlias (PortalID, HttpAlias) VALUES (<YourPortalID>, 'http://yoururl')
    • Restart the site by restarting the application pool or restarting IIS
      1. Check IIS and make sure your site is running with the correct permissions.
      2. Check IIS and verify that the correct version of the .NET Framework is installed in the application pool on the site.

If all this fails ...

I had limited success by renaming the Install directory to something else, say _Install and hitting the site again so that I can see what an ASP.NET error is. After I started the site again, I will return its original name.

Good luck

+6
source

It will be a long story, but I will try to keep it small:

Assuming you have correctly configured the localhost / dotentnuke site, please back up your database before trying:

  • Look at the PortalAlias ​​table in the database and look at the entries with portalID = 0
  • Delete all entries for portal 0 and change one entry to point to localhost / DotNetNuke
  • Try running the URL again.

Keep in mind that portalAlias ​​is the table in which dnn looks, and portal 0 is the default portal, so this must be at least one entry for portal 0 in the portal alias.

Since you have a dnn instance with multiple portals, you need to create a separate website for each if they are the parent portals. and change httpalias to your local iis url for each portal.

Let me know if you need any other help.

0
source

More articles:


All Articles