RTE giving error after upgrade from 4.8>4.10.1>4.11.6
Hi All
I've just finished an upgrade from 4.0 to 4.11.6. Somwhere between the steps from 4.8 > 4.10.1 > 4.11.6 the Rich text editor in the backoffice all of the sudden throws the below error. If I change the datatype of my property then the node is displaying fine in the backoffice.
This is the ysod message thrown
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:
[NullReferenceException: Object reference not set to an instance of an object.]
I have tried to delete the temp files in the /TEMP/ClientDependency folder and to increment the version number in the /config/ClientDependency.config file as well but without any luck.
I got something like the first error after a similar upgrade. My problem was that I had forgotten to copy the FileSystemProviders.config file into the config folder.
Thanks guys, the file was present in the config folder but the section was missing in the web.config file.
However I now get this screen instead...
No provider found with the alias 'media'
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.ArgumentException: No provider found with the alias 'media'
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.
H5IS, Bjørn was spot on - forgot to add <FileSystemProviders configSource="config\FileSystemProviders.config" /> in the <configuration> section.
However now I get this...
Input string was not in a correct format.
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.FormatException: Input string was not in a correct format.
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.
...turns out I had deselected all possible options in the configuration of the datatype doing some testing earlier today. It's now configured and it works! Yay!
RTE giving error after upgrade from 4.8>4.10.1>4.11.6
Hi All
I've just finished an upgrade from 4.0 to 4.11.6. Somwhere between the steps from 4.8 > 4.10.1 > 4.11.6 the Rich text editor in the backoffice all of the sudden throws the below error. If I change the datatype of my property then the node is displaying fine in the backoffice.
This is the ysod message thrown
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:
[NullReferenceException: Object reference not set to an instance of an object.]
Umbraco.Core.IO.FileSystemProviderManager.<GetFileSystemProvider>b__1(String s) +34
System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory) +72
Umbraco.Core.IO.FileSystemProviderManager.GetFileSystemProvider(String alias) +52
Umbraco.Core.IO.FileSystemProviderManager.GetFileSystemProvider() +130
umbraco.editorControls.tinyMCE3.webcontrol.TinyMCEWebControl..ctor() +160
umbraco.editorControls.tinyMCE3.TinyMCE..ctor(IData Data, String Configuration) +342
umbraco.editorControls.tinyMCE3.tinyMCE3dataType.get_DataEditor() +100
umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +93
umbraco.controls.ContentControl.CreateChildControls() +709
System.Web.UI.Control.EnsureChildControls() +102
umbraco.controls.ContentControl.OnInit(EventArgs e) +32
System.Web.UI.Control.InitRecursive(Control namingContainer) +140
System.Web.UI.Control.AddedControl(Control control, Int32 index) +197
System.Web.UI.ControlCollection.Add(Control child) +79
umbraco.cms.presentation.editContent.OnInit(EventArgs e) +1253
System.Web.UI.Control.InitRecursive(Control namingContainer) +140
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +480
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
In the console log I get this error, when clicking a node: GET http://olf2011.localhost/umbraco/editContent.aspx?id=1154 500 (Internal Server Error)
And after a period of time the umbracotimeout stuff throws an error like this:
Uncaught TypeError: Object function () {
umbraco.presentation.webservices.legacyAjaxCalls.initializeBase(this);
this._timeout = 0;
this._userContext = null;
this._succeeded = null;
this._failed = null;
} has no method 'GetSecondsBeforeUserLogout'
I have tried to delete the temp files in the /TEMP/ClientDependency folder and to increment the version number in the /config/ClientDependency.config file as well but without any luck.
Also did a re-run on the permissions...
Looking forward to receive some pointers.
Cheers,
Jan
Hi,
I got something like the first error after a similar upgrade. My problem was that I had forgotten to copy the FileSystemProviders.config file into the config folder.
Cheers
Bjørn
... and make sure that the config is referenced in your Web.config (as a <section>)
http://our.umbraco.org/forum/getting-started/installing-umbraco/34859-Error-after-reverting-upgrade
Thanks guys, the file was present in the config folder but the section was missing in the web.config file.
However I now get this screen instead...
No provider found with the alias 'media'
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.ArgumentException: No provider found with the alias 'media'
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.272
Hi,
Have you also added the configuration section:
http://our.umbraco.org/forum/getting-started/installing-umbraco/34436-49-imagesmedia-broke?p=1#comment127239
Cheers
Bjørn
Hi Jan, what do you have inside the FileSystemProviders.config?
There should be an entry for the "media" provider.
Cheers, Lee.
H5IS, Bjørn was spot on - forgot to add <FileSystemProviders configSource="config\FileSystemProviders.config" /> in the <configuration> section.
However now I get this...
Input string was not in a correct format.
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.FormatException: Input string was not in a correct format.
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.272
...turns out I had deselected all possible options in the configuration of the datatype doing some testing earlier today. It's now configured and it works! Yay!
Thanks a bunch for your help guys, you rock!
/Jan
Cool :)
Cheers
Bjørn
is working on a reply...