I'm afraid it's not quite clear to me what the video illustrates - I can't see if you're uploading all the necessary files and folders after the upgrade? I think that the issue might be that not all files have been overwritten in the /bin, /umbraco and /umbraco_client folders? And perhaps you need to merge the /config/ files as well?
Otherwise it might be a good idea to bump the version number in the /config/ClientDependency.config file and recycle the application pool and see if that helps.
Now set debug=true in web.config then load the Unbraco UI and type "Umbraco.Sys.ServerVariables" into the Chrome Javascript console and post what it shows.
That does work but you shouldn't run in production with it set to debug=true.
With it in debug mode now and logged into Umbraco, you need to use the Chrome Console and execute "Umbraco.Sys.ServerVariables" then we can hopefully work out from the result what might be the cause.
Ah ok, the error is coming from the EventCalendar package. It looks like it was recently fixed in this commit but not yet released (you might need a custom build or speak to the author if a release is imminent).
Umbraco 7.2.4 Upgrade error No url found for api name legacyTreeJs
Hi,
Old Version 7.1.8
New Version 7.2.4
Upgrade
I explained my problem in the link below
http://www.screencast.com/t/gp4Y9Gcp
Help Please!
Critical!!!
Note: Log File include:
2015-04-25 23:15:11,393 [16] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 113] An unhandled exception occurred System.ArgumentException: Aynı anahtara sahip öğe zaten eklenmiş. konum: System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) konum: System.Collections.Generic.Dictionary
2.Insert(TKey key, TValue value, Boolean add) konum: EventCalendarBelle.ServerVariableEvents.Parsing(Object sender, Dictionary2 e) konum: Umbraco.Web.UI.JavaScript.ServerVariablesParser.Parse(Dictionary2 items) konum: Umbraco.Web.Editors.BackOfficeController.ServerVariables() konum: lambda_method(Closure , ControllerBase , Object[] ) konum: System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) konum: System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary2 parameters) konum: System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary2 parameters) konum: System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() konum: System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass81.Hi Mücahit
I'm afraid it's not quite clear to me what the video illustrates - I can't see if you're uploading all the necessary files and folders after the upgrade? I think that the issue might be that not all files have been overwritten in the /bin, /umbraco and /umbraco_client folders? And perhaps you need to merge the /config/ files as well?
Otherwise it might be a good idea to bump the version number in the /config/ClientDependency.config file and recycle the application pool and see if that helps.
/Jan
Hi Mücahit,
I think the issue you have is the same as described here?
Do you have the YouTube package installed?
Jeavon
Hi Jeavoni, I have the YouTube package installed. Thank you
Hi Jan, I do it all.
Old ClientDependency.config file :
New ClientDependency.config file :
Look Please: http://www.screencast.com/t/piLyEoXaJ
Help!!
Ok, if you update the YouTube package to v1.0.3 it should fix it...
I could not solve the problem!
Ok, so you updated YouTube to v1.0.3?
Now set debug=true in web.config then load the Unbraco UI and type "Umbraco.Sys.ServerVariables" into the Chrome Javascript console and post what it shows.
Jeavon
Hi Jeavon,
in web.config :
change
It worked.
Thank you...
That does work but you shouldn't run in production with it set to debug=true.
With it in debug mode now and logged into Umbraco, you need to use the Chrome Console and execute "Umbraco.Sys.ServerVariables" then we can hopefully work out from the result what might be the cause.
It should be something like the below.
Ah ok, the error is coming from the EventCalendar package. It looks like it was recently fixed in this commit but not yet released (you might need a custom build or speak to the author if a release is imminent).
Ok Jeavon.
Thank you for the answer.
is working on a reply...