OK I reinstalled the blog 4 umbraco, It apparently didn't install correctly the first time. It did this time. Except now when I go to the main content page I get
Could not load control: '/usercontrols/Blog4Umbraco/CommentModeration.ascx'. Error message: System.Web.HttpParseException (0x80004005): The server tag 'asp:UpdatePanel' is ambiguous. Please modify the associated registration that is causing ambiguity and pick a new tag prefix. at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at umbraco.cms.presentation.dashboard.OnInit(EventArgs e)
Any idea's? I'm kind of guessing a version conflict of some kind. In CommentModeration.ascx line 2
Also when I actually try and create a blog post and save it, all I get is:
An error occurred while processing your request.
Is there a log somewhere so I can see what is actually going on? Does anyone know what is going on?
I really really want to like Umbraco, but it has given me nothing but issues since installing it. I was able to get by most except these issues with the blog. Maybe I'll use something else for the blog.
Also, the unhelpful "error occured" message is popping up, I'm guessing, because error reporting on screen has been disabled in the latest release due to a recently discovered .net exploit.
to switch it back on try finding the customErrors tag in your web.config file and setting it to something like
Ya actually that dawned on me last night that the custom error is probably hiding what's going wrong. As for the commentmederation.ascx I fixed that. I used MS web install on my host to install Umbraco, and either that or loading up the site in IIS added/changed the web.config. I compared the online version and a local version and changed all the dll references to ver=4.0.0.0. Seemed to fix the ambiguity issue.
I think its because my server appears to be running .Net 4.0 by default, and umbraco doesn't support 4.0 at the moment. Its doubly annoying, as I've never had any problems like this with Umbraco before. It normally installs and runs as sweet as a nut.
Blog problems
OK I reinstalled the blog 4 umbraco, It apparently didn't install correctly the first time. It did this time. Except now when I go to the main content page I get
Could not load control: '/usercontrols/Blog4Umbraco/CommentModeration.ascx'.
Error message: System.Web.HttpParseException (0x80004005): The server tag 'asp:UpdatePanel' is ambiguous. Please modify the associated registration that is causing ambiguity and pick a new tag prefix. at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at umbraco.cms.presentation.dashboard.OnInit(EventArgs e)
Any idea's? I'm kind of guessing a version conflict of some kind. In CommentModeration.ascx line 2
<%@ Register Assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI" TagPrefix="asp" %>
Is that correct?
Also when I actually try and create a blog post and save it, all I get is:
An error occurred while processing your request.
Is there a log somewhere so I can see what is actually going on? Does anyone know what is going on?
I really really want to like Umbraco, but it has given me nothing but issues since installing it. I was able to get by most except these issues with the blog. Maybe I'll use something else for the blog.
I've noticed that when you reinstall the blog it tends to duplicate the entries in the config/dashboard.config file.
Removing the dupes doesn't seem to have resolved the issue for me though, so I'll keep looking.
Also, the unhelpful "error occured" message is popping up, I'm guessing, because error reporting on screen has been disabled in the latest release due to a recently discovered .net exploit.
to switch it back on try finding the customErrors tag in your web.config file and setting it to something like
<system.web>
<customErrors mode="Off" />
</system.web>
It should then give you some sensible errors.
Ya actually that dawned on me last night that the custom error is probably hiding what's going wrong. As for the commentmederation.ascx I fixed that. I used MS web install on my host to install Umbraco, and either that or loading up the site in IIS added/changed the web.config. I compared the online version and a local version and changed all the dll references to ver=4.0.0.0. Seemed to fix the ambiguity issue.
Ok I fixed it. After I turned off custom errors I got
"Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted"
So I added <httpRuntime requestValidationMode="2.0" /> to the system.web part of web.config and it worked. Man what a pain.
Yep, I had to do the same.
I think its because my server appears to be running .Net 4.0 by default, and umbraco doesn't support 4.0 at the moment. Its doubly annoying, as I've never had any problems like this with Umbraco before. It normally installs and runs as sweet as a nut.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.