Page Revision History error
When attempting to view a particular page's revision (version), our customError page is loaded (404), not the revision. The exception in the logs is: An exception of type 'System.NullReferenceException' occurred and was caught.
Message : Object reference not set to an instance of an object.
Source : Telerik.Sitefinity
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : Void InitializeSiteMapDataSource()
HResult : -2147467261
Stack Trace : at Telerik.Sitefinity.Web.UI.NavigationControls.LightNavigationControl.InitializeSiteMapDataSource()
We have restarted the site and app pool, same results.
Any ideas?
Hello,
The described problem seems to be caused by a known issue in Sitefinity. This kind of problem appears every time when there is a navigation control placed on a page or a template. We have already logged a bug in our feedback portal where you can track the its status.
Navigation Control throws error in revision history
Unfortunately there is no workaround available for this bug. I can assure you that our developers are aware about it. The status in our feedback portal will be changed as soon as this bug is fixed.
Regards,
Stefani Tacheva
Telerik
Has this been fixed in version 7.0?
Hi,
The problem is fixed in Sitefinity 7.0. To resolve the problem you need to upgrade your project to this version. More information about the upgrade procedure could be found in our Sitefinity documentation.
Regards,
Stefani Tacheva
Telerik
Is there a fix for Sitefinity 8.2? We've recently updated but are receiving a similar error for all of our pages.
Hi Katharine,
Judging by the error message the issue occurs in your custom control with namespace SitefinityWebApp.PrimaryResource. You may have deleted this custom control but it may still be present and used on the revision history version you are trying to view and this might be causing the issue.
If you still have this control registered in Sitefinity, what you can try is to drop it on a test new page and check the behavior when you view the page on the frontend or when you open the page for edit. This way you can see if the issue will be reproduced. If yes, this means that the issue is caused in the InitializeControls() method of the custom control and it is not related to the issue which is currently discussed in this forum thread.
Regards,
Sabrie Nedzhip
Telerik