Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...GetSkins Stored Procedure after UpgradeGetSkins Stored Procedure after Upgrade
Previous
 
Next
New Post
8/27/2010 10:04 AM
 
After upgrading from 4.9.5 to 5.5 I noticed that the Stored Procedure GetSkins is pointing to a column named PortalID. This column no longer exists in the Skins table. Is there a list somewhere that shows the schema for DNN 5.5? Is the Stored Proc wrong or the Table wrong? Or are these just not used anymore?

The only columns are SkinID, SkinPackageID, and SkinSrc.

Thanks
 
New Post
9/1/2010 4:09 AM
 
it's a good question, and the answer is that I'm not 100% sure - skins are full extensions in 5.0 and above, so it's likely the table and it's sprocs are redundant, and should be removed. Please log an issue at support.dotnetnuke.com and we can investigate further and make any necessary changes.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/1/2010 7:59 AM
 
I happened to run into that same issue last evening when attempting to publish via scripting an upgraded datbase to GoDaddy via their SQL Data Publishing Web Service. The Skins table was modified in DNN 5.00.00 and both the GetSkins and GetSkin stored procedures which reference the PortalID column of the "old" Skins table were replaced by stored proceedures of different name. For some reason, they were never deleted in the 5.00.00.SqlDataProvider script nor in any later version scripts. You can safely delete both GetSkins and GetSkin from the database.

Normally, having those stored procedures left over in the database would not be an issue as they are never executed by code. However, when publishing the datbase via scripting, they will cause the publishing to fail.

Let me know if you will be logging the issue to Gemini or if you want me to.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
9/1/2010 9:56 AM
 
Thanks for the information. I created an issue for this (DNN-13705).
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...GetSkins Stored Procedure after UpgradeGetSkins Stored Procedure after Upgrade


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out