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 ...Any short term workaround for DNN-6601?Any short term workaround for DNN-6601?
Previous
 
Next
New Post
3/1/2015 11:29 PM
 

Hi,

Our site is basically locked from making changes in many areas because of DNN-6601 on 7.4. Note that this problem was not created from creating and deleting a portal. When we installed DNN some years ago, we simply installed DNN and created a new portal. Portal 0 was never created if I remember correctly.

I saw the DNNTurbo scripts, but our site is fairly small and I am concerned about needing to go through extra steps each time I upgrade with it (not to say it is not worth having, but we do not have many pages on our site). So until 7.41 is released, is there anything we can do to get rid of the error? Rolling back the site is not really an option now.

Thanks,

Steve

 
New Post
3/2/2015 4:33 AM
 
you need just to copy lines 1744 to 1755 from TurboDNN740.sql (IF .... END) and paste into text box in Host > SQL and click Execute.
You may remove Portal 0 in Host > Website Management, once the bug is fixed (scheduled for 7.4.1)

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/2/2015 7:07 AM
 

Thanks Sebastian for the quite helpful post. If I remember, a portal 0 was never created, and the counter started at 1 when I went in to create a portal. Maybe at the time... I think it was DNN 5, I really did not need to create a portal, as it was only going to be a single website but I was more green about DNN then. So when I did create a portal, it started at 1. Now, maybe I am wrong and I deleted a portal 0, but I never remember that. I am saying this as other sites may be in the same situation we are in.

 Thanks again,

 Steve

 
New Post
3/2/2015 7:41 AM
 
Steve, due to the install routine, a portal 0 is always created, but you are able to delete and a couple of users did.
DNN should be able to handle it, but a bug was introduced in DNN 7.4.0, which causes the issue.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/2/2015 10:07 AM
 

I tried to report this bug issue to your bug reporting website at https://dnntracker.atlassian.net/secure/Dashboard.jspa but there is no option in there to create a new issue and when I try to register there I get an error that no more licenses are available for registration. Am I missing a button or option some where on that dashboard to open a new issue?

This appears to be a pretty major bug that we reproduced in 2 different DNN 7.4.0 (353) version sites. This error occurs when you try to create a new Parent or Child site using an exported Portal Template. The problem does not occur when selecting either the "Blank" or "Default" Website Templates instead.

1) Went to "Host -> Site Management" and chose "Export Site Template". Checked all option boxes, applied name and description and clicked "Export Template".

2) Template and Resources files were created properly without issue in the /Portals/_default/ folder as they should be.

3) Clicked "Add New Site" button. Filled in applicable information and selected my new Template file from the "Template" dropdown box. Clicked "Create Site".

4) Site creation process starts as normal and runs for about 5-10 seconds and then the following error message is reported at the top of the Add Site window:

Error parsing Website TemplateObject reference not set to an instance of an object. at DotNetNuke.Entities.Portals.PortalController.ParseTemplateInternal(Int32 portalId, String templatePath, String templateFile, Int32 administratorId, PortalTemplateModuleAction mergeTabs, Boolean isNewPortal, LocaleCollection& localeCollection) at DotNetNuke.Entities.Portals.PortalController.CreatePortalInternal(Int32 portalId, String portalName, UserInfo adminUser, String description, String keyWords, PortalTemplateInfo template, String homeDirectory, String portalAlias, String serverPath, String childPath, Boolean isChildPortal, String& message)

Intended Result: New Parent Site should have been created using the exported Template and Resources file.

Upon searching the domain's folder structure it was discovered that a new Portals sub folder named "1" had been created for the new site and there are entries for the new portal in the "Portals" table of the database as well as other portal related tables within the database. However, inspecting those database tables it is clear that the operation was incomplete as many fields are set to "NULL" or do not exist at all when compared to the default 0 Portal within the tables.

- Further testing on a brand new DNN 7.4.0 (353) installation resulted in the exact same error and results.

- We also attempted to create a new Parent Site using a different Portal template file from a skin we had just purchased and that portal template file also reproduced the exact same error and results.

- We then setup a new DNN 7.3.4 installation and were able to create a Parent Site using the portal template from our purchased skin package without any issues at all. So the issue seems isolated to version 7.4.0.

This is a very major issue as it appears new Sites within 7.4.0 cannot be created using any templates other than the "Blank" or "Default" website templates including within DNN. We have a customer who urgently needs to create 7 new Parent Sites within their DNN 7.4.0 installation using an Exported Portal Template from the default 0 portal they have designed over the last few weeks. Please help us to resolve this bug/issue asap. We unfortunately are on a time table to roll out these new Parent Sites and cannot wait for DNN to release a newer version of the platform that fixes this bug. I am a technician with good experience and knowledge, I can follow any solution steps provided to resolve this issue.

We searched the bug reporting site you have and found very similar bugs reported in DNN 7.3.4 pertaining to Portal Templates using other languages that was fixed in 7.4.0. We believe this issue may be similar or even the same.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Any short term workaround for DNN-6601?Any short term workaround for DNN-6601?


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out