What version of Umbraco are you using? This bug started happening in 4.10 and have been fixed in 4.11.4 where you also need to run a "path fixup" script when you're done upgrading the installation.
we are using umbraco v 4.7.1.1 (Assembly version: 1.0.4393.24044)
Its a e-commerce site lots of other packages is installed
we installed "path fixup" package to our current version but its shows error
Could not load control: '/App_Plugins/PathFixup/PathFixDashboard.ascx'. Error message:System.Web.HttpCompileException (0x80004005): d:\Boossh_Websites\sastage\App_Plugins\PathFixup\PathFixDashboard.ascx(12): error CS0012: The type 'System.Web.Mvc.UrlHelper' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. at System.Web.Compilation.AssemblyBuilder.Compile() 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 umbraco.cms.presentation.dashboard.OnInit(EventArgs
when we install mvc on our server can it cause server related or site related issue ?
Ok, as I wrote above you should only run the fixup package if you upgraded to 4.11.4. As I also wrote there has been a bug introduced in 4.10 that causes this error.
But since you're running 4.7 it's because of something else that this happens.
Are you doing some custom stuff with the API that could be the cause of this?
Value cannot be null. Parameter name: attribute
Hi ,
when publishing a new node show error " Value cannot be null. Parameter name: attribute "
itried /Umbraco/dialogs/republish.aspx?xml=true and umbraco.config replaced but doesn't solved the issue
regards mithun
Hi Mithun
What version of Umbraco are you using? This bug started happening in 4.10 and have been fixed in 4.11.4 where you also need to run a "path fixup" script when you're done upgrading the installation.
Looking forward to hear more from you.
/Jan
Hi Jan,
we are using umbraco v 4.7.1.1 (Assembly version: 1.0.4393.24044)
Its a e-commerce site lots of other packages is installed
we installed "path fixup" package to our current version but its shows error
Could not load control: '/App_Plugins/PathFixup/PathFixDashboard.ascx'.
Error message: System.Web.HttpCompileException (0x80004005): d:\Boossh_Websites\sastage\App_Plugins\PathFixup\PathFixDashboard.ascx(12): error CS0012: The type 'System.Web.Mvc.UrlHelper' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. at System.Web.Compilation.AssemblyBuilder.Compile() 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 umbraco.cms.presentation.dashboard.OnInit(EventArgs
when we install mvc on our server can it cause server related or site related issue ?
please help
Thanks & regards
Mithun
Hi Mithun
Ok, as I wrote above you should only run the fixup package if you upgraded to 4.11.4. As I also wrote there has been a bug introduced in 4.10 that causes this error.
But since you're running 4.7 it's because of something else that this happens.
Are you doing some custom stuff with the API that could be the cause of this?
/Jan
Hi jan,
All the steps are done through manually(Create document type ,Node etc).its a large site 18000+ nodes.
I already faced this issue on 1 month ago,replaced the umbraco.config file solve that issue.But this time im not lucky.
Any way to solve this issue is much appreciated.
regards
mithun
Hi Jan,
Please check the below link.it will explains 4.7 versions has this issue....
http://www.simonantony.net/knowledge-base/articles/value-cannot-be-null-parameter-name-attribute-error-in-umbraco/
http://our.umbraco.org/forum/developers/extending-umbraco/31531-Examine-Error-In-Latest-Version-Of-Umbraco
http://www.blogfodder.co.uk/2012/5/11/hashed-links-value-cannot-be-null-parameter-name-attribute
http://our.umbraco.org/m?mode=topic&id=23212
http://issues.umbraco.org/issue/U4-913#tab=Comments
regards
mithun
Hi
I had the same problem, just upgrade umbraco to latest version ) In my case it was 4.11.5
is working on a reply...