I thought that perhaps some of the modules weren't up-to-date and that this might have something to do with some of the problems. So I updated all that were in use, deleted a few not in use, so now all modules are at most recent version and the DNN install is as well at 4.5.1.

Then I tried to export the portal to a template, and re-create it on another DNN 4.5.1 install where I haven't had any such problems.

The export seemed to go fine, but when I try to import, I get this very long and rather interesting error message ... and the contents definitely seem to relate to the errors I have received as noted above (re: user permissions). Can someone tell me what I need to do to rescue my install?

Ah ... looks like this is something else ... a bug in 4.5.1 which is addressed in 4.5.2:

- in Portal Template Export, removed nodes which would cause it not to validate against the schema on import. The offending nodes were related to properties added to the the ModuleInfo class and Permissions classes in DNN 4.5.

template is not a valid Portal Template File.

so ... the import issues are not necessarily related, but the DotNetNuke.Security.Permissions.Controls.FolderPermissionsGrid.GetUsers

problem still remains even after upgrading all modules. :(

Maybe C. Nurse knows something about it ... from dotnetnuke.xml:

<member name="M:DotNetNuke.Security.Permissions.Controls.FolderPermissionsGrid.GetUsers">
 -----------------------------------------------------------------------------
 <summary>
 Gets the users from the Database
 </summary>
 <history>
     [cnurse]    01/12/2006  Created
 </history>
 -----------------------------------------------------------------------------

</member>

Ok, let's see if we can bring this monologue to an end ...

Apparently it is not a problem to have filenames with spaces? I note that the core DNN skins have many examples.

I have always counseled my clients to avoid spaces in folder names and file names.

Is it more of a sin to have a space in a folder name? After loads of investigation of the matters presented in this conversation with myself, I discovered a client had created a folder with a space in the name. I corrected it as well as some filenames in the same folder that also had spaces. Then I deleted references to all files in the files table (not all, just in the folder in question), and to the folder in the folders table.

Still I couldn't re-synch (object not found ...) for a while ... I figured caching and such, and came back to it a couple hours later. I was able to delete entries from the Event Viewer, which was a good sign ... then I was able to re-synch recursively, even better ... and finally was able to link correctly to the files so users can download.

This may be a temporary state - it seems to go back and forth. But maybe the space in the folder name was the culprit behind it all, and it is the real fix. It was really a problem - affected not only the portal in question, but all portals on the instance. They all worked or didn't work in the same way at the same time.

This is, I hope, my final contribution to this thread ... maybe someone can provide a definitive opinion on whether a space in a folder name could be the cause for all of this. If so ... how do y'all keep clients from doing this?