I have a sick portal with lots of orphaned links - I note that when I can manage to link to files via FCK Editor that the path is now /Portals/2/Docks/myDoc.pdf instead of LinkClick.aspx?.... etc.

All of the links that use the LinkClick format are broken, and I am unable to edit them except on rare occasion. I cannot even delete the module where they occur nor delete the page to try to recreate it.

I've scrutinized the folders and files tables as well as the physical directory and these are in synch. But many orphaned links exist on the portal, and I (and client\) regularly get errors about "DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Permissions.Controls.FolderPermissionsGrid.GetUsers() at DotNetNuke.Security.Permissions.Controls.PermissionsGrid.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() "

I have had repeated problems regarding this. Current version is at DNN 4.5.1. Compression is turned off for this portal. I expect I can delete pages in the database but not sure I want to get into that; probably going to rebuild this portal in another DNN install and drop this one entirely. Tired of messing with it. But I am wondering how FCKEditor is supposed to be making links to files - using regular path values, or the LinkClick control?

Thanks -

Mauricio,

I think I got this resolved. I believe it was an issue between the version of Snapsis PageBlaster I was using interacting with AJAX in the file manager related to compression in PageBlaster. I did two things: upgraded to PageBlaster (I think 2.2.4) and also set page persistence to Page instead of Memory. I did both of these at the same time, roughly, and am uncertain which made the difference; or perhaps it was both together.

All seems to be working well at this time; it has been a few days now with no errors or problems.

Thanks for your response!

Michael