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...Administration ...Administration ...Error on updating an HTML moduleError on updating an HTML module
Previous
 
Next
New Post
8/3/2010 7:58 AM
 
Thanks.

I don't recall any errors, but ...

I looked through the install package for the HTML module.  It looks like items related to HtmlTextLog were added in 05.01.00.  Do you think that the best way to handle this would be to execute manually the sequence of DataProvider SQL files beginning with that one?  



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
8/3/2010 10:25 AM
 
It appears that only the 05.01.00.SqlDataProvider script creates or alters the foreign key relationship betweeen the HtmlTextLog and HtmlText tables. The way the script is constructed, rerunning it will not re-create the FK relationship if the HtmlTextLog table already exists.

I would take a look at the database to see if

1. HtmlTextLog table exists. If not, you may want to try rerunning the scripts.
2. There is a FK relationship between HtmlText table (primary key table) and HtmlTextLog table (foreign key table) on the ItemID field with on cascade delete enabled. If not, I would rerun the portion of the 05.01.00.SqlDataProvider script that creates this FK relationship:


ALTER TABLE {databaseOwner}{objectQualifier}HtmlTextLog WITH NOCHECK ADD CONSTRAINT
      FK_{objectQualifier}HtmlTextLog_{objectQualifier}HtmlText FOREIGN KEY
      (
       ItemID) REFERENCES {databaseOwner}{objectQualifier}HtmlText
      (
       ItemID) ON UPDATE NO ACTION
                     ON DELETE CASCADE
                     NOT FOR REPLICATION

I would, however, also be concerned that the two other statements which set up the FK relationships between HtmlTextLog and WorkflowStates tables and between the HtmlTextUsers and HtmlText tables might not have run as they are in the same GO block.

Regarding the issue occuring in a new module instance on the 6th and following version revisions, the module retains a default of 5 maximum versions. It would not be until the 6th and following revisions that an attempt would be made to delete the oldest version each time a new version is created. Although the module code can retrieve it's maximum number of versions to retain from the portal settings, it does not appear that there is any user interface for setting a different value - hence the defaut of 5 is always used.

It also appears that the FK constraint error is preventing any version from being deleted from the HtmlText and HtmlTextLog tables as the module instance first having problems contains 18 versions.

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
8/12/2010 2:32 PM
 
Thanks very much for your comments. I got into the database and basically followed along with the SqlDataProvider script. I found that I needed to add ON UPDATE NO ACTION ON DELETE CASCADE NOT FOR REPLICATION at several places in the database. After that, DotNetNuke is normal again.



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Error on updating an HTML moduleError on updating an HTML module


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