Products » Support Forums 

Support Forums

HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl MasterWildcard Extensions and URL MasterWildcard Extensions and URL Master
Previous
 
Next
New Post
11/19/2009 2:58 AM
 

No, the licence does not affect the operation of the module in any way.  All the licence does is add or remove the 'unlicensed' message.  It is not the problem in this case.

Can you send me the url of the actual site (with hte module enabled) so I can take a look?  Also, if you can post the 'FriendlyUrl' section from your web.config, I'll check to see if anything is wrong.

 
New Post
11/19/2009 5:17 PM
 

Currently, for testing purposes, we only have the URL Master module enabled on our dev (localhost) site, so you wan't be able to access it. You can see how it's supposed to work by going to www.mybitesite.com and do a search for '34243'. When the results are displayed, click one of the restaurant names. This is where the following details page comes up blank with the module enabled, but funtions properly when it is disabled. Also, when the module is enabled, and we just try to go to a standard module (such as via the Login link), DNN resolves the name to http://localhost/dnnmbs/login?returnurl=%2fdnnmbs%2fdefault.aspx and we get the following error:

 

 HTTP Error 404.0 - Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

We then have to manually change the URL to http://localhost/dnnmbs/login.aspx and it displays/functions properly.

Here is the 'FriendlyUrl' section from web.config:

defaultProvider="iFinity.UrlMaster">providers>clear />add name="iFinity.UrlMaster" type="iFinity.DNN.Modules.UrlMaster.DNNFriendlyUrlProvider, iFinity.UrlMaster.FriendlyUrlProvider" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="HumanFriendly" redirectUnfriendly="false" doNotRewriteRegex="/DesktopModules/|/Providers/|/LinkClick\.aspx" doNotRedirectRegex="/LinkClick\.aspx|/Providers/|/DesktopModules/" doNotRedirectSecureRegex="" pageExtensionUsage="AlwaysUse" parameterHandling="OrderedParameters" ignoreFileTypesRegex="(?<!linkclick\.aspx.+)(?:\.pdf$|\.gif$|\.png($|\?)|\.css$|\.js($|\?)|\.jpg$|\.html$|\.htm$|\.axd($|\?)|\.swf$|\.flv$|\.ico$|\.xml($|\?))" checkForDupUrls="true" forceLowerCase="false" spaceEncodingValue="%20" redirectWrongCase="false" rebaseClientPath="false" autoAsciiConvert="false" triggerDictionaryRebuildRegex="&ctl=tab|/ctl/tab|/Admin/Tabs/|/ctl/Signup" useBaseFriendlyUrls="/SearchResults;/ModuleDefinitions;" deletedTabHandling="Do301RedirectToPortalHome" doNotRedirect="" sslClientRedirect="True" logCacheMessages="False" cachePersistRestart="False" cacheTime="1440" pageExtension="" />add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="humanfriendly" />providers>friendlyUrl>

 

<friendlyUrl

 
New Post
11/20/2009 12:33 AM
 

Ok, if the url like http://localhost/dnnmbs/login?returnurl=%2fdnnmbs%2fdefault.aspx doesn't work properly, then something isn't set up correctly.  The web.config section you show above is enabled for always use extensions, but the 'pageExtension' field has no value.  I suspect this might be the problem.  Either change the 'pageExtensionUsage' to 'Never' or change the pageExtension value to .aspx to restore operation.  You can either do this directly through the web.config or you can do it through the 'friendly url settings' page.

 
New Post
11/20/2009 3:18 PM
 

Yep, that did it. Setting the module to 'Never use page extensions' got the login screen back, and a change to the 'Friendly URL Settings' fixed the blank screen. So, I think we're good now. Btw, I think what happened is that I tried the 'Never' setting, and something didn't work right, and so I switched it back. I never expicitly cleared the 'pageExtension' field, so I think it is cleared when you change to the 'Never' setting. Since I didn't notice this happening, I didn't expect that I needed to add aspx back in as the default. Just FYI...

Thanks much for the help -- we'll most likely purchase a license shortly.

 
New Post
11/20/2009 10:39 PM
 

Unfortunately, we're still running into a couple issues. Initially, we started evaluating Url Master for the purpose of short Url names for specific records on our site. So, instead of www.mybitesite.com/home/tabid/70/RestID/349/source/34243/default.aspx we want www.mybitesite.com/burgerking. I may be doing this wrong, but I was under the impression that to do this, you first create a new page under Admin | Pages, and call it "BurkerKing". Under the page's Advanced Settings, we change the Link Url setting to 'URL' and paste the entire 'long' Url (as above). But when we go to this short url, there is no content (i.e.: blank). This was working previously -- but we had to include the .aspx extension (i.e.: burgerking.aspx). So, we enabled wildcard extensions, but it doesn't seem to be functioning anymore.

 
Previous
 
Next
HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl MasterWildcard Extensions and URL MasterWildcard Extensions and URL Master


Support Guidelines.. Please read before posting

To get support on iFinity products and services, please search the forums for the the answer to the problem you are seeking. If you cannot find a solution, post a question in the relevant forum.   Ensure that you specify the relevant versions of the problem, and the actual error message or a detailed description of the problem.    You will need to register with this site to post on the forum.  If you have a Microsoft Live (Hotmail/Passport) account you can use that.  If you have a Open Id account you can use that.  If you neither of these, you will need to register a user Id and password.

Please note : If you are posting a new thread for the Url Master module, please include the following information where applicable:

- Url Master version

- DotNetNuke version

- Example Url where possible

- If there is an error, please post the full error text and/or stack trace (from the DotNetNuke event log).