DotNetNuke

Re: DNN Only Works with localhost

diveblue — Fri, 21 Jan 2005 17:02:25 GMT

I'm having the same issue....does not appear that turning off friendly urls resolves the problem, nor does turning caching off.

Re: DNN Only Works with localhost

jhenning — Wed, 19 Jan 2005 15:27:47 GMT

The menus pulling the wrong alias is a know issue we are working on. Basically we cache the tabs collection, which currently contains the absolute url. See this issue.

I believe if you turn FriendlyURLs off your problem will be corrected. If not, then wait until the next release.

Re: DNN Only Works with localhost

sitary — Tue, 18 Jan 2005 21:09:15 GMT

Hi,

I'm encountering a similar issue using 3.08. I developed my site on //localhost/MyDnnSite and it works fine. I want to host it at //MyDnnSite.MyDomainName.com on another server. I copied over the web files and the db. I can login and navigate to most pages as a user but as an admin or host when I try to change Admin settings the only page that I see is the home page. Also, when I click on Register or the Administrator account, I get "An error has occurred." message. When I try to change the SuperUser account settings, the page is blank. When I try to change any Host settings, I get this familiar error:

[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo)
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo)
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e)
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

So I tried changing PortalAlias.HTTPAlias, first by adding MyDnnSite.MyDomainName.com to the string, and when that did not work, replacing it. Still no joy.

Any thoughts on where I've gone wrong?

Thanks,

Simon

Re: DNN Only Works with localhost

Geert — Sat, 15 Jan 2005 07:55:00 GMT

You should use machinename/DotNetNuke as your first alias (on dnn 2.1.2 at least, not sure if necessary on 3.0.8)

Re: DNN Only Works with localhost

nettech — Sat, 15 Jan 2005 02:58:59 GMT

Bob,
Sounds like you need to update your portal aliases. I'm guessing DNN 3.x from what you described. Access the site via localhost. Login as host and select Site Settings from the Admin menu. On the bottom of the site settings page you will see "Add New HTTP Alias". Click that link and then enter machinename/dotnetnuke in the text box Click update.

On DNN 2.1.2 the steps are similar. Login as host and select Site Settings from the Admin menu. Down near the bottom you will see the portal alias box. Add ,machinename/dotnetnuke after localhost/dotnetnuke and click Update.

Hope that helps.

Will

DNN Only Works with localhost

RobertLair — Sat, 15 Jan 2005 02:18:59 GMT

Hello everyone,

Not sure if this is something simple, an environment issue, or what, but I thought I would try to save some time by pinging the list. I have been using DNN locally via http://localhost/dotnetnuke.... However, now that I am ready to allow other people to hit it remotely, DNN is not working as expected. Basically, you get to the home page if you browse via http://machinename/dotnetnuke, but all the tabs go back to the home page. Any ideas?

Thanks!
Bob