iFinity

Written by:
Wednesday, July 29, 2009 2:45 PM 

DotNetNuke 5.1.1, Community and Professional Editions, has just been released. 

See http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2304/DotNetNuke-5-1-1-Released.aspx for more details.

With the release of DNN 5.1.1 (CE & PE), there’s a small incompatibility with the Url Master module.   This affects sites upgraded to DNN 5.1.1 from any version.  The symptom will be an inoperable website on some pages, with an associated cryptic database related error message.  The incompatibility relates to the inclusion of a new property of ‘HasChildren’ in DotNetNuke tabs.

I have developed and tested a fix for this problem, and it is available now, in the Url Master Release 1.14.09. 

You can download the latest release of the Url Master module from the Url Master Product Page.  All existing customers are requested to upgrade to the latest version prior to upgrading their DotNetNuke sites to 5.1.1 (or later versions, when they come out).

Already Upgraded to DNN 5.1.1?

If you’ve already upgraded to DNN 5.1.1 with the Url Master module in place, you’re probably looking at (and searching) an error like this:

500 Server Error

An error occured during processing : if possible, check the event log of the server

Administrators : Obtain more information by changing to debug mode and switching custom errors off in the configuration.

Error Reading DataReader Expecting - DotNetNuke.Entities.Tabs.TabInfo. Returned - TabID, TabOrder, PortalID, TabName, IsVisible, ParentId, Level, IconFile, DisableLink, Title, Description, KeyWords, IsDeleted, Url, SkinSrc, ContainerSrc, TabPath, StartDate, EndDate, RefreshInterval, PageHeadText, IsSecure, PermanentRedirect, SiteMapPriority, CreatedByUserID, CreatedOnDate, LastModifiedByUserID, LastModifiedOnDate, IconFileLarge,

If that’s the case, here’s the steps to get your site back and working again:

0) Open up your web.config for editing. 

1)  Locate the 'UrlRewrite' entry in the web.config.  If you're running IIS5/6, it will be in the <system.web> section.  If you're running IIS7, it will be in the <system.webserver> section.

Remove this entry:

<add name="UrlRewrite" type="iFinity.DNN.Modules.UrlMaster.UrlRewriteModule, iFinity.UrlMaster.FriendlyUrlProvider" />

and replace it with this entry:

<add name="UrlRewrite" type="DotNetNuke.HttpModules..UrlRewriteModule, DotNetNuke.HttpModules" />

2) Locate the 'DNNFriendlyUrl' section.  This will be the same regardless of the IIS version.

Search for ‘<friendlyUrl defaultProvider="iFinity.UrlMaster">’

Change the value for defaultProvider from ‘iFinity.UrlMaster’ to ‘DNNFriendlyUrl’

Ensure that this entry remains in the web.config file.  If it isn’t present, add it back in, inside the ,<friendlyUrl></friendlyUrl> section.

<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="HumanFriendly" />

3) Save your web.config, and your site should be running again.

4) Go to the Module Definitions page, and upload the 1.14.09 version of the Url Master module.  Check the install logs to make sure that it upgraded OK.

5) Re-Enable Url Master in the Friendly Url Settings page.

Your site should be running again.

Trackback Print

Tags:

Categories:

Location: Blogs Crafty Code

Your name:
Your email:
	(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Add Comment   Cancel