Last night I was working on finishing one project, when frontend started to fail. The crazy thing about this error, is that I've only been working with CSS files. The Backoffice works, but everytime I wanna see the frontend I get this :
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Umbraco.Web.UmbracoContext.get_UmbracoUser()
Hi!
Last night I was working on finishing one project, when frontend started to fail. The crazy thing about this error, is that I've only been working with CSS files. The Backoffice works, but everytime I wanna see the frontend I get this :
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248
Hi Srdjan Lukic-Bardak,
Sometimes this kind of error occurs when you have 2 users with same name. So check your uses and in that case you need to rename the user.
And also check in your css that if any tag is missing or not. Means check css file that it has error or not.
Hope this helps.
Regards,
Urvish Mandaliya
Urvish -> Sorry for late feedback.
It was the cache in Chrome browser that was giving this error.
is working on a reply...