I've just taken the plunge and upgraded from 4.9.5 to 5.4.2. Everything is going OK so far, discovering what's new and changed in DNN 5, until now.

Before the upgrade I used to create my own skins in what I consider to be the normal way, skin files in (for example) Portals/_default/Skins/MySkin and container files in Portals/_default/Containers/MySkin. 

After the upgrade, when I try to update any of my skins details (Host > Extensions > Edit (MySkin) > Update Extension) it fails with a SQLException "Cannot insert duplicate key row in object 'dbo.Packages' with unique index 'IX_Packages'.".

Looking at the dbo.Packages table and the dbo.UpdatePackage stored procedure I can see why. Both the skins and containers for MySkin have a package name of 'MySkin' but with different PackageTypes (Skin and Container respectively). The dbo.UpdatePackage stored procedure uses the package name as the key in the where clause, so it updates two rows, creating the duplicate key violation. 

I've created a temporary fix for myself by adding "[PackageType]= @PackageType" to the where clause.

Has anyone else come across this or do I have a problem with my upgrade?

Cheers,
Rhys

---

www.rmjcs.com - Mostly SQL Server Stuff

Thanks for the quick response.

I'll do a little more work around the problem then log it as an issue.

Rhys

---

www.rmjcs.com - Mostly SQL Server Stuff

 
Thanks, Rhys!  That mod to the UpdatePackage() stored procedure fixed the problem nicely.

WHERE [Name] = @Name AND [PackageType]= @PackageType

-- Christo