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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Navigation DoesnNavigation Doesn't Work Under Apache with mod_aspdotnet
Previous
 
Next
New Post
9/16/2006 7:22 AM
 

I'm new to DotNetNuke, I'm just messing about with the installation at present to see if it's at all compatible with Apache on Windows XP Pro. 

I'm attempting to install version 4.3.4 on apache 2.  The installation goes without a hitch.  The default website comes up, but I when clicking on any local links such as Login (http://<domain>/Home/tabid/36/ctl/Login/Default.aspx) I just get the IE default "Page does not exist" error.

What type of things should I be looking for?  It all works fine when I use IIS. I'm struggling to identify how the navigation is working as even in IIS http://<domain>/Home/tabid/36/ctl/Login/Default.aspx doesn't exist as a path on the server, but it works fine when I click the link.  I suspect by reading the docs there's some underlying navigation system/provider.  I may just need to configure it in Apache.  I also fear that I may be out of luck as I've just read that mod_aspmodnet plugin for Apache is only supposed to work with .Net 1.1 (athough I do have 2.0 sites running), but there may be 2.0 server features missing (I'm assuming).

Sorry if I've babbled on,  I've tried to mention all the factors that I have floating around my head.  I'm really quite stuck for a direction.

Any help or advice on how the navigation system works will be appreciated.  I haven't seen Apache and DotNetNuke mentioned in many places at all, so any tips and theories will be investigated.

Thanks,
  Nanook

 
New Post
9/16/2006 5:21 PM
 

You'll probably need to turn off Friendly Urls.

If you can get it running under Apache then mod_rewrite would probably be better anyway.

If you can get to the DB, look for the HostSettings table and set FriendlyUrls to 'N'

 


DotNetNuke Modules from Snapsis.com
 
New Post
9/17/2006 1:18 PM
 

Yey, right on the button.  That fixed it, I think that would have taken me a while to find.

I have a scripting error now though.  When I try to change the password for one of the default users, I click on the "Change Password" link and get a javascript error - "WebForm_PostBackOptions is undefined".  I don't know if this is a mod_dotnetmod error (being .Net 1.1 and not 2.0), I think some of the required scripts are missing.

I'll look in to it and checkout mod_rewrite as well.

Thanks for your help,

Nanook

 
New Post
9/18/2006 2:32 AM
 

Glad I could help.   It'll be interesting to hear your results on getting it running on Apache for windows.

That next error is most likely because you need a folder in the website called "aspnet_client" which holdes th JS scripts for client-side validation in .Net 1.1  this script folder is usually placed there by the asp.net install, or running aspnet_regiis.exe, I wonder if there is a aspnet_regapache.exe with that mod :)
Regardless, you can get the folder of any windows IIS site that was setup to run ASP.Net 1.1

For .Net 2.0 the same scripts are generated dynamically (and virtually) by a call to WebResource.axd

 


DotNetNuke Modules from Snapsis.com
 
New Post
9/19/2006 5:13 PM
 

Yey, it's working, I've been searching the net for ages reading up on how the whole WebResource.axd thing works and just how to get javascript postbacks to work on Apache (I really thought more people would be using .net on Apache)

What you suggested was exactly what I thought, the only problem was I knew there were no .js client files with Asp.Net v2.  I first searched my pc for axd files, nothing of interest was returned. I was about to give up then I thought there might be some handlers missing from my Apache "httpd.conf" file so I opened IIS and added many missing .Net v2 ones and restarted Apache.  No change, I wasn't really expecting any.

After a bit more research I found an article that mentioned that if you want to debug javascript located by an .axd reference you could just put the link in the browser window like so:

http://<domain>/WebResource.axd?d=2-lANzFnJ1awZfk3eZZ-NQ2&amp;t=632866956950430144

The browser prompted me to save out a file called "WebResource.axd".

I opened up the file in a text editor and it was the javascript, the first line reading "function WebForm_PostBackOptions...".   I was unconvinced I would be able to use this file without renaming it to a JS file and reworking all the pages that included it instead of the axd request, but I thought I'd have an unoptomistic attempt at just dropping it in to the root of my site, and you believe it actually worked?

I'm still a bit confused.  I don't know if it's ignoring the the query string after the "?" and just loading the .axd file or if Apache is using mod_aspdotnet as a handler (it's configured too) and processing it.  I don't really care, this is just a play project.

No doubt this won't be the last thing that isn't fully working.

Thanks for your help John.  If you want to play with this configuration I can help you set it up.  Maybe others will try Apache as an alternative, I've only used Apache and .Net for a few low usage websites, but the response times are noticably VERY fast.

Cheers,
  Nanook

 

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Navigation DoesnNavigation Doesn't Work Under Apache with mod_aspdotnet


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