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 StartedNew to DNN Plat...New to DNN Plat...Risks of changing from Classic to IntegratedRisks of changing from Classic to Integrated
Previous
 
Next
New Post
9/20/2011 11:27 AM
 
Hey, dunno if anyone can help me here.

I have been stuck with this problem for weeks now, removing the page extension for 1 single page on my site. Just to make it look nicer on posters etc.

The address is right now example.com/products.aspx, I want that address to become example.com/products   The rest of the site can still have .aspx

My first attempt have been making a folder named products in root and then put a default.aspx file in the folder and redirect it to the correct page. That doesnt work however, when I enter the default file in that folder I just get redirected to the root domain, not example.com, but webspace2.example.com

Anyone know why this doesnt work? Or how to make it work? 

Well so now to my other problem, I decided I would try iFinity's module to get rid of it, but it requires me to either configure a wildcard, but I can't access my server via IIS-tool, because I'm on a shared server. But I can switch it to Integrated pipeline instead of Classic. But it have tons of warning saying some of my application pools might not work etc etc... 

Now I just want to know, what could happen if I switch it to Integrated, and what should I look to change before doing it?

Appriciate all help, this problem have been following me for weeks now and it's really itching!

Thank you!

Patrik


 
New Post
9/21/2011 9:37 PM
 
what warning text are you being shown - i switch from classic to integrated (and back) all the time with little issue - there are a few items to be aware of (e.g. occasionally modules can fail - this is pretty rare, but one that does work in classic but not integrated is the active directory provider - thought this is fixed in the next release.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Risks of changing from Classic to IntegratedRisks of changing from Classic to Integrated


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