Hello,
I've moved a big (and very old) installation onto v9 last week (from 8.x). At the time, things seemed to be super smooth: new persona features looked good and much faster, I could edit pages, etc.

However, trying to learn how to use the new environment revealed some problems. I'll mention two and describe in detail just the one that looks more worrying.

1. Only way I could find to create pages in a given part of the tree is to use the "create multiple pages" function. The mask to add just one page only allows to add to the root. Is this by design? (As some of the comments I've read around here seem to suggest?)

2. "Site assets" and "Global Assets" both send me to an error page in the form of "https://domainname/cms/404b.htm?aspxerrorpath=/cms/cms/Default.aspx". Which is interesting, upon inspection (see below)!

 While investigating the second issue, I noticed that going directly to the tab that includes the FileManager (DAM)  (as in /cms/Default.aspx?tabid=XXX, bypassing the persona bar altogether) worked for "site/file management" (I assume equivalent to "Site Assets"), but not for "host/file management" ("Global Assets"?). The error returned for the latter is:

 Error: File Management is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.DigitalAssets.Components.Controllers.DigitalAssetsController.GetFolderViewModel(IFolderInfo folder) at DotNetNuke.Modules.DigitalAssets.Components.Controllers.DigitalAssetsController.GetRootFolder(Int32 moduleId) at DotNetNuke.Modules.DigitalAssets.View. (EventArgs e) --- End of inner exception stack trace ---

Indeed, looking at the database (and comparing with a clean v8 install I have in a test box) there was no entry for root folder (which I understand is "\portals\_default"). I've tried to add a record for it, only to find that upon visiting the tabid in question, the filemanager did show up, but displayed an error. Concurrently, the corresponding record in the Folders table gets deleted (?!?).

Thing I've noticed is that in the error path I see above (using the persona link) an additional "/cms" is added, which sent me to the IIS logs, where I could confirm that clicking on the two persona links in question is actually trying to open "/cms/cms/Default.aspx?tabid=xxx" which understandably throws a 404 error as the path is wrong and the file does not exist.

In short, issue 2 seem to contain two embedded issues: the first is that for some reason the "/cms" bit of the base URL gets repeated, the second is that I can't find a way to make the folder structure of the Global Assets reappear (believe me: I've tried in many different ways, omitted for brevity).

Any help appreciated!

Thanks,
Sergio

Thanks Sebastian,

I've tried manually browsing to "hostname/cms/default.aspx?tabid=XXXX&portalid=0". Unfortunately, it didn't work: doing so without creating a new record for the root folder generates the same error as before. Doing the same after generating the row shows the file/asset manager with just the root. Trying to do anything therein makes an error "pop up", trying to reload the page generates the same exception as above.

On inspection, the new record I'm creating actually gets deleted the moment I visit the page. After that, I suppose it's not surprising that things don't work. So for me the question would be: "why does DNN remove the manually created record in the 'folders' table"?

Thanks again,
Sergio