TheShaner
Nuke Newbie
Posts:4
 |
| 02/28/2011 10:23 AM |
|
I just migrated my DNN 5.01 install from a server2000 IIS6 server to a server2008 IIS7. Everything is working great, with the exception of one small but important detail. When I create new pages, I get 404 errors when trying to navigate to them. It is odd, I can hit any other page created previously, but nothing new. has anyone ever seen this before?
|
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/28/2011 12:45 PM |
|
Can you tell which URL is being used for the new pages? |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
TheShaner
Nuke Newbie
Posts:4
|
| 02/28/2011 12:47 PM |
|
The new URL's are coming back looking as they should ... http://domain/parent/childpage.aspx, just not resolving. Here are some details on the environment if it helps ... DNN v5.01.04 (3) We were at the cap for upgrades because of the old environment. We did this upgrade in part because we needed to upgrade past this version. We have not upgraded yet though. ASP.net is running 3.5, and yes this was an upgrade from 2.0 Here are the web.config lines for these: - - -
One thing that I find a little odd about the Friendly URL's is that I looked for an installed instance of this module/extension and could not find it installed. It is working though as the other URL's of existing pages don't have tabid's in the path. I set this up a while ago and my memory escapes me, but it seems as if I did not install a module to execute this. Is it a built in funciton? Any new page will throw the error, but for example, if I create the page urltest in the page manager, I will get an error back on http://domain/urltest.aspx. Thank you for the help! |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/28/2011 12:52 PM |
|
Check your portalalias entries. Also look at the Admin,Pages page to make sure that the new pages are where you think that they should be. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
TheShaner
Nuke Newbie
Posts:4
|
| 02/28/2011 12:58 PM |
|
Let me try the code again ... - <section name="friendlyUrl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
- <add name="UrlRewrite" type="iFinity.DNN.Modules.FriendlyUrl.UrlRewriteModule, iFinity.FriendlyUrlProvider" />
- <friendlyUrl defaultProvider="iFinity.FriendlyUrl">
<providers>
<clear />
<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="HumanFriendly" />
<add name="iFinity.FriendlyUrl" type="iFinity.DNN.Modules.FriendlyUrl.DNNFriendlyUrlProvider, iFinity.FriendlyUrlProvider" includePageName="true" regexMatch="[^\+a-zA-Z0-9 _-]" urlFormat="HumanFriendly" redirectUnfriendly="true" doNotRedirect="SearchResults;" checkForDupUrls="true" forceLowerCase="false" redirectWrongCase="false" replaceSpaceWith="_" logCacheMessages="false" />
</providers>
</friendlyUrl>
|
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/28/2011 1:09 PM |
|
I'm not really familiar with URLMaster. You'll need to check how you have it configured. That could be part of the problem. But, you might want to check with iFinity's support as they will certainly know a lot more about the product. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
TheShaner
Nuke Newbie
Posts:4
|
| 02/28/2011 1:27 PM |
|
I am not acutally using URL Master, just friendly URL, which I believe is part of the build after 4.5. Regardless, I just put that in there to be thurough, I dont believe that has anything to do with it personally. I am able to rename pages, and the current pages are being rewritten to human friendly URL's just fine, so I suspect that isnt the problem.
My aliases are all the same as they were and cover all bases. Only new pages are affected.
In the page manager, the pages show up exactly as they should.
Any other thoughts? |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 03/03/2011 10:03 AM |
|
Is this still a problem? If so, can I look at the site? |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
paul bellman
Nuke Newbie
Posts:3
|
| 03/29/2011 3:03 PM |
|
Have you solved this. I am running a custom dnn 3.x on framework 1.1. we just moved from win2k3 to win2k8r2 with iis7.5 we are getting that 404 error all the time with urls that have end-user input like searching. I narowed it down to FriendlyURL line
If (pair(1).Length > 0) Then
ELSE
pathToAppend = pathToAppend & "/" & System.Web.HttpUtility.UrlEncode((Chr(32)).ToString())
END IF
they are putting a chr(32) which is a space, then url encoded puts a + sign in there. the url looks like this domainName.com/tabid/122/module/search/searchterm/+/default.aspx
for some reason the + is the offensive char. if I put in an underscore it works, but some of my code relies on no input, so I don't know what to do. I think it is an ii7 thing, but have you found anything else?? |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 03/29/2011 3:11 PM |
|
I'm afraid that my experience doesn't even go back to DNN 3.x!
Seriously, I assume that there are good reasons that you haven't or aren't able to upgrade. I'd suggest that you ask your question over on the DotNetNuke forums. It's possible that someone there may be able to help you. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
paul bellman
Nuke Newbie
Posts:3
|
| 03/29/2011 4:03 PM |
|
thanks for the reply. I believe iis7 doesn't like + signs in the url. apparently, in later versions of this urlrewrite software there is a value in the web.config to replace a space with %20, but I tried that and it fails. in above code I did this,
pathToAppend = pathToAppend & "/%20"
but it fails.
what do common re-writers do today when there is a blank input? and yes, this dnn install is a total abortion, but it runs the most critical client software. we will migrate to another platform later in the year, because I find it painful to work in vs2003 these days. |
|
|
|
|
paul bellman
Nuke Newbie
Posts:3
|
|
Joseph Craig
DNN MVP
Posts:11667
|
|