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 ...Bug in export/page permissions? 4.3.5Bug in export/page permissions? 4.3.5
Previous
 
Next
New Post
9/19/2006 8:54 AM
 
I upgraded to 4.3.5 yesterday, and exported my main portal out as a template (with content).

Upon creation of a new portal using this template, I got this error:

Error parsing Portal TemplateObject reference not set to an instance of an object. at DotNetNuke.Services.FileSystem.FolderController.UpdateFolder(FolderInfo objFolderInfo) at DotNetNuke.Services.FileSystem.FolderController.UpdateParentFolder(Int32 PortalID, String FolderPath) at DotNetNuke.Services.FileSystem.FolderController.AddFolder(Int32 PortalID, String FolderPath, Int32 StorageLocation, Boolean IsProtected, Boolean IsCached) at DotNetNuke.Entities.Portals.PortalController.ParseFolders(XmlNode nodeFolders, Int32 PortalId) at DotNetNuke.Entities.Portals.PortalController.ParseTemplate(Int32 PortalId, String TemplatePath, String TemplateFile, Int32 AdministratorId, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal)

The portal still seemed to create OK. However when I try to create a new page in it, the default permissions are set so that 'All Users' have 'View' and 'Edit' permissions.    I cannot turn these 2 checkboxes off as they are greyed out.  This cannot be correct?      Currently if an anonymous user were to hit the portal homepage, they would have edit permissions; not good.




 
New Post
9/20/2006 6:20 PM
 

I'm seeing this same error, although I haven't tried logging into the portal (another can of worms entirely).  Here is the post I have in the Benefactors forum (sorry for the duplicate post core team.... just trying to get noticed):

I'm having trouble adding a portal using a template from another DNN install. 

DNN_L: a local install of 4.3.5; runs fine

DNN_H: a hosted install of 4.3.5; runs fine (has a production site already)

1. Export DNN_L with content

2. FTP two appropriate files to hosted site

3. Login to DNN_H, Add portal choosing the DNN_L template

--I can create a portal based on one of the standard DNN templates

--I cannot delete any of the portals that are 'partialy' created

--unable to add portal on another 4.3.5 install (3rd unique host) based on this template

--unable to add portal on localhost (DNN_L) based on this template

--no exceptions found in the log

--tried exporting again; 2nd export fails to load the same as the first

--tried exporting w/out content; loads fine in all scenarios

I think the problem originates with the exporting of the template or maybe even file/database synchronization.  On further investigation I renamed the portal.template.resources file to portal.template.resources.zip and opened it with winzip.  I noticed right away that several folders were missing, and confirmed via ftp that they were not created on the target host (DNN_H).  Then I logged into DNN_L (localhost) and went to Admin/File Manager.  Sure enough the folders missing from my exported resources file didn't show up.  I tried a recursive sync from the root.  No luck.  I manually synched each folder, and they started showing up.  While manually synchronizing all the folders I also noticed several folders that didn’t exist on the file system, but were showing up in DNN.  When I tried to manually remove them I received a “folder already removed” error message.  If I recreated the folder (and subfolders) on the file system, then retried the delete, that worked.  Lot’s of work here before I try another export.  I’ll edit this post again after I’m done.  OK, one thing I noticed although I’m not sure if it’s related.  My IE began to respond slower and slower and I finally had to close and open a fresh browser session to get things moving again.  ... Well, so much for that theory.  I manually ensured all folders and files are in sync, and still the same error message.  I did notice that the portal export function doesn’t include folders if they are empty (which is bad).  I added a placeholder.txt file to correct that issue.  Still no luck.

I’m stumped.  Any ideas?  Any suggestions I might try?  Any troubleshooting tips?

 

Error Message:

Error parsing Portal TemplateObject reference not set to an instance of an object. at DotNetNuke.Services.FileSystem.FolderController.UpdateFolder(FolderInfo objFolderInfo) at DotNetNuke.Services.FileSystem.FolderController.UpdateParentFolder(Int32 PortalID, String FolderPath) at DotNetNuke.Services.FileSystem.FolderController.AddFolder(Int32 PortalID, String FolderPath, Int32 StorageLocation, Boolean IsProtected, Boolean IsCached) at DotNetNuke.Entities.Portals.PortalController.ParseFolders(XmlNode nodeFolders, Int32 PortalId) at DotNetNuke.Entities.Portals.PortalController.ParseTemplate(Int32 PortalId, String TemplatePath, String TemplateFile, Int32 AdministratorId, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal)

 

 

 
New Post
9/21/2006 4:25 AM
 
Nice to know i'm not going nuts.

I tried a couple variations; portal template with content and without content, both made this same error on import. Upon trying to delete these portals, it also generates a generic .NET App error, and I find that the Portals and their content are still in the DB (although the physical number directory tree of the portal seems to have been deleted).

I have managed to get the portal template w/content working, albeit every module and page I add still defaults to All Users > View & Edit.       This means I have to go into the DB for each one and fix these permissions manually.

Someone pointed out that these permissions are what are normally applied to the Admin account (as in, Admin can always View & Edit and you can't turn it off).    So somehow the adition of this 'All Users' rolegroup to 4.3.5 has mixed up the roles? Confused..


 
New Post
9/21/2006 12:48 PM
 
Do you recall what you did to get it working?
 
New Post
9/21/2006 2:09 PM
 
Oh the portal 'worked' the first time.    An error screen and screwy default permissions seem like a bad start though.. but I have no choice i've been waiting months for the release of 4.3.5 specifically to fix this issue.. and it looks like it hasn't.

So far I've done most 'normal' activities, such as adding modules, pages, etc. and things seem ok (other than the permissions).

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Bug in export/page permissions? 4.3.5Bug in export/page permissions? 4.3.5


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