Important Notice! DotNetNuke 3.0.13

Scott McCulloch posted on April 06, 2005 09:56

The DotNetNuke 3.0.13 upgrade (from 3.0.12) drops the primary key on the users table. This has caused problems with two of my modules, Private Messages & News Articles. Since they reference the users table via foreign key.

Before you upgrade, ensure you are at a version of News Articles (00.02.07 or later) and Private Messages (01.00.04 or later). These releases drop the foreign keys referencing the user table.

Don't worry if you have already upgraded, it doesn't really bust the installation, just logs in the sql script saying that it couldn't drop or create the primary key (because it already exists).

Posted in: Announcements, Modules, Bugs, News Articles

Actions: E-mail | Permalink | Comments (3)

| Kick it! | DZone it! | del.icio.us

Post Rating

12345

Comments

# Bradley Molzen

Wednesday, April 06, 2005 11:09 AM

FYI - If you've followed Scott's HTTP Compression instructions... you must also disable the blowery compression before upgrading.

That means... use the web.config that was supplied with the 3.0.13 package.... do the upgrade.... then put back in the custom edits after the upgrade completes successfully.

# Anonymous User

Wednesday, April 06, 2005 4:16 PM

This is the same for PM (and possibly for where are they). I reckon its something in the install that it should be doing. So I'll have to release updates of those modules too.

# Anonymous User

Wednesday, April 06, 2005 5:46 PM

It does not apply to where are they.

Post Comment

Name (required)

Email (required)

Website

Enter the code shown above:

Notify me of followup comments via e-mail

Important Notice! DotNetNuke 3.0.13

Related Articles

Post Rating

Comments

Post Comment