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 ...create a mobile create a mobile 'view-only' interface to my DNN site
Previous
 
Next
New Post
10/14/2008 7:10 PM
 

I want to create a mobile version of a dotnetnuke website. Now, I have no intention of administrating the website on a mobile phone. I just want to be able to view the pages and modules. The modules, skins and containers will be all specifically designed to render well on a mobile phone. 

Basically I need two seperate 'interfaces' to the dotnetnuke website. One 'web' interface for administrating the site. And another mobile interface to view the pages. My main issues is this: I do not want to use a <form runat="server"> control on the mobile interface. But obviously it is required on the 'web' interface so that all the DNN controls will continue to work.

The general idea is to create a new Mobile.aspx page which performs much the same of the Default.aspx page, but without the DNN:form control. So how do I choose which page should be used when a request comes into the site....

I intend to use www.mycompany.com as the URL for the Website, and m.mycompany.com as the URL for the mobile site. How I should I configure this in IIS etc.... Do I need two seperate DNN installations which access the same database (is this even possible?) ?

Or can I rewrite the incoming request based on the host which the request is accessing?

I do NOT want to rewrite the request based on the User-Agent.

If anyone can provide help on the above problems please let me know....thanks!

-Darragh

BTW: I have looked at the MobiNuke module on snowcovered which goes a long way to solving my problems, but I'd prefer NOT to use 3rd party software if possible.

 
New Post
10/15/2008 2:51 AM
 

not sure i understand what you want here. the <form> tag is required in any asp.net forms application (which dnn is). You cannot remove it (well, you can but the application will stop working)


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
10/15/2008 11:42 AM
 

As far as I know, I would highly recommend looking at MobiNuke, as I think it gets a good portion of what you want, and it will save time and testing as it has already been tested.

You can handle the multiple urls, by just adding an alias in DNN for the other site and then point it in IIS to the same path using a header.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/15/2008 6:15 PM
 

[QUOTE]ErikVB wrote

not sure i understand what you want here. the

actually the form tag is not required in an asp.net forms application. it is only requited when certain controls are being used....such as input controls and buttons. however, if i'm just using things like labels, repeaters, images, links, etc... then the form tag is not required. in my mobile 'view-only' interface these are the only controls i'm intending to use. the main advantage of removing the form tag is becuase there is no v13wstat3. but also a lot of phone have problems rendering complex forms.

 
New Post
10/15/2008 6:20 PM
 

Mitch Sellers wrote

As far as I know, I would highly recommend looking at MobiNuke, as I think it gets a good portion of what you want, and it will save time and testing as it has already been tested.

You can handle the multiple urls, by just adding an alias in DNN for the other site and then point it in IIS to the same path using a header.

 

as i mentioned, i have looked at the mobiNuke module and it is very good. however, i really want to have as much control as possible over the html, doctypes, content-types etc which are output. also i would like to control how mobile devices are detected. for example mobiNuke appears to use WURFL for device properties, but where I work we have our own propriety device database.

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...create a mobile create a mobile 'view-only' interface to my DNN site


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