Hi,
I've upgraded my umbraco version from 7.4.3 to 7.11.1 and from some reason, I get
Could not load type 'umbraco.loadDictionary' from assembly 'umbraco, Version=1.0.6750.39773, Culture=neutral, PublicKeyToken=null'.
I tried removing all entries from my trees.config file, and surprisingly enough, it had no affect.
Is it possible that the loadDictionary is being called from another file? How can it be that deleting the trees.config had no affect what so ever on the other trees? (content, media etc.)
So after confirming you have this change in your trees.config file, the question is what or how is it still trying to load your dictionary from the previous umbraco.loadDictionary config settings.
Usual things to check:
1) Increase the ClientDependency version in the /config/ClientDependency.config
(we want to ensure the upgraded site is using the latest set of javascript, particularly as the angular dictionary rewrite will have added new stuff)
2) Old dlls in bin folder, just confirm there aren't any old versions of the umbraco dlls in your bin folder after the upgrade...
3) Application pool recycle, make sure the site has been recycled since you made the configuration change.
Failing that for sanity sake I'd download a vanilla version of Umbraco 7.11.1 and point it at your upgraded db, is all fine - then try to spot any differences in the configuration.
Thanks for your help.
I've increased version number in ClientDependency.config from 1 to 2
<clientDependency version="2"
and recycled the iis pool,
but I still get the same frustrating error.
How can it be?
Trying to download a vanilla version of umbraco is not a viable option for me, as I need to create a new project for it.
I hope you have another idea.
the only clue I have, is that if I delete the content of trees.config, the umbraco still behaves the same, as if he doesn't even read content from that file..
the error i see in console:
)]}', {Message: "An error has occurred.",…}
ExceptionMessage
:
"Could not load type 'umbraco.loadDictionary' from assembly 'umbraco, Version=1.0.6750.39773, Culture=neutral, PublicKeyToken=null'."
ExceptionType
:
"System.TypeLoadException"
Message
:
"An error has occurred."
StackTrace
:
" at Inetdesign.ExportImportDictionaryItems.BootStrapper.BaseTree_NodeActionsCreated(Object sender, NodeActionsEventArgs e)
↵ at umbraco.cms.presentation.Trees.BaseTree.OnNodeActionsCreated(NodeActionsEventArgs e)
↵ at umbraco.cms.presentation.Trees.BaseTree.Initialize()
↵ at Umbraco.Web.Trees.ApplicationTreeExtensions.TryGetRootXmlNodeFromLegacyTree(ApplicationTree appTree, FormDataCollection formCollection, UrlHelper urlHelper)
↵ at Umbraco.Web.Trees.ApplicationTreeExtensions.TryGetRootNodeFromLegacyTree(ApplicationTree appTree, FormDataCollection formCollection, UrlHelper urlHelper, String currentSection)
↵ at Umbraco.Web.Trees.ApplicationTreeController.<GetRootForMultipleAppTree>d__1.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at Umbraco.Web.Trees.ApplicationTreeController.<GetApplicationTrees>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__3`1.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()
↵--- End of stack trace from previous location where exception was thrown ---
↵ at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
↵ at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
↵ at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()"
Suspect the import / export dictionary package from Inetdesign (https://our.umbraco.com/projects/developer-tools/export-import-dictionary-items/) is not compatible with 7,11 remove the DLL for that package and any configuration and you should be ok...
I've deleted the Inetdesign.ExportImportDictionaryItems.dll from the root\bin folder, and also deleted the Inetdesign.ExportImportDictionaryItems folder from root\Umbraco\Plugins and Presto! problem solved!!
Thank you man, Let's hope that it will help someone else along the way.
Trees.config issue
Hi, I've upgraded my umbraco version from 7.4.3 to 7.11.1 and from some reason, I get
I tried removing all entries from my trees.config file, and surprisingly enough, it had no affect.
Is it possible that the loadDictionary is being called from another file? How can it be that deleting the trees.config had no affect what so ever on the other trees? (content, media etc.)
I tried clearing cache BTW.
Thanks, Rotem
Hi Rotem
This appears certainly connected to the rewrite of the Dictionary Section into AngularJS in Umbraco 7.11
https://github.com/umbraco/Umbraco-CMS/pull/2159 & http://issues.umbraco.org/issue/U4-5683
As part of this rewrite the configuration for where the dictionary tree should be loaded from has changed:
has become:
So after confirming you have this change in your trees.config file, the question is what or how is it still trying to load your dictionary from the previous umbraco.loadDictionary config settings.
Usual things to check:
1) Increase the ClientDependency version in the /config/ClientDependency.config
(we want to ensure the upgraded site is using the latest set of javascript, particularly as the angular dictionary rewrite will have added new stuff)
2) Old dlls in bin folder, just confirm there aren't any old versions of the umbraco dlls in your bin folder after the upgrade...
3) Application pool recycle, make sure the site has been recycled since you made the configuration change.
Failing that for sanity sake I'd download a vanilla version of Umbraco 7.11.1 and point it at your upgraded db, is all fine - then try to spot any differences in the configuration.
regards
Marc
Hi Marc,
Thanks for your help. I've increased version number in ClientDependency.config from 1 to 2
and recycled the iis pool, but I still get the same frustrating error.
How can it be?
Trying to download a vanilla version of umbraco is not a viable option for me, as I need to create a new project for it.
I hope you have another idea. the only clue I have, is that if I delete the content of trees.config, the umbraco still behaves the same, as if he doesn't even read content from that file..
the error i see in console:
Suspect the import / export dictionary package from Inetdesign (https://our.umbraco.com/projects/developer-tools/export-import-dictionary-items/) is not compatible with 7,11 remove the DLL for that package and any configuration and you should be ok...
cough
If you want a modern Umbraco 7 package that allows you to export / import dictionary items then check out - https://our.umbraco.com/projects/backoffice-extensions/diplo-dictionary-editor/
Marc, Your'e a genius!!!
I've deleted the Inetdesign.ExportImportDictionaryItems.dll from the root\bin folder, and also deleted the Inetdesign.ExportImportDictionaryItems folder from root\Umbraco\Plugins and Presto! problem solved!!
Thank you man, Let's hope that it will help someone else along the way.
is working on a reply...