Now getting another error when opening a content or media picker:
Compiler Error Message: CS0618: Warning as Error: 'umbraco.dialogs.treePicker' is obsolete: 'Use the TreeControl instead. This does however get used by the TreeService when requesting the tree init url.'
Replaced all of /bin /umbraco and /umbraco_client folders from newly downloaded 4.7 from codeplex and still getting errors.
Media picker dialog is giving me this error:
Compiler Error Message: CS0618: Warning as Error: 'umbraco.controls.ContentPicker.Text' is obsolete: 'Use Value property instead, this simply wraps it.'
I've not seen this specific problem before... but seems weird that you're getting these "Warning as Error" exceptions.
Do you have any classes in your App_Code?
Thinking that there might be something trying to compile at app-start/runtime? As any compiled assemblies would get that error flagged at compile time in Visual Studio right?
My guess is that one of those where one of the core team reckon a method should be obsolete - but there is so much legacy code, it's simplier to keep it in place. To me the Obsolete attribute just means there's a newer/better method in place - not that the existing method is broken.
Error appeared out of nowhere in the Back Office dialogs
I am getting the following error when opening "Manage Hostnames" or any macro dialog:
Compiler Error Message: CS0618: Warning as Error: 'umbraco.helper.Request(string)' is obsolete: 'Use umbraco.Presentation.UmbracoContext.Current.Request[key]'
Nothing has changed since yesterday.
the site was upgraded from 4.0.3 to 4.7.. all was good until this morning.
Now getting another error when opening a content or media picker:
Compiler Error Message: CS0618: Warning as Error: 'umbraco.dialogs.treePicker' is obsolete: 'Use the TreeControl instead. This does however get used by the TreeService when requesting the tree init url.'
Any suggestions?
do you remember making any changes lately? do you get any error in the umbracoLogs table?
I only installed uComponents last night.. that was it.
The dialogs were working then... site is secured so noone can touch it.
This morning I got these errors.
uninstalled uComponents, but problem is still there.
how about checking if uComponents is the problem,can you copy the website to your computer and try removing uComponents ?
Already did that.. no go!
I'm comparing /umbraco folder to base 4.7
compare also umbraco_client
try also to copy the basic dlls of umbraco 4.7 to your bin directory (interfaces.dll cms.dll etc)
Check bin for dlls that don't belong. Maybe sort by date added or compare to a fresh 4.7 install.
Copied over 4.7 assemblies.. still have the error
Replaced all of /bin /umbraco and /umbraco_client folders from newly downloaded 4.7 from codeplex and still getting errors.
Media picker dialog is giving me this error:
Compiler Error Message: CS0618: Warning as Error: 'umbraco.controls.ContentPicker.Text' is obsolete: 'Use Value property instead, this simply wraps it.'
Hi Daniel,
I've not seen this specific problem before... but seems weird that you're getting these "Warning as Error" exceptions.
Do you have any classes in your App_Code?
Thinking that there might be something trying to compile at app-start/runtime? As any compiled assemblies would get that error flagged at compile time in Visual Studio right?
Cheers, Lee.
app_code is empty... anything else?
Is there any stack-trace? Guessing not, otherwise you would have posted it.
Could there be any way that any of the files got reverted back to v4.0.x? I'm clutching at straws here - sorry.
- Lee
found the problem...
<providerOption name="WarnAsError" value="true" />
Changed to:
<providerOption name="WarnAsError" value="false" />
Don't know why that was on...
Glad that you got it sorted! Phew!
Cheers, Lee.
Thanks to your comment about it being a warning.. gave me direction to look in.
This issue showed me that some of the pages are using obsolete methods... shouldn't the core team fix those?
Event the contentpicker trees are using obsolete methods.
Not sure.
My guess is that one of those where one of the core team reckon a method should be obsolete - but there is so much legacy code, it's simplier to keep it in place. To me the Obsolete attribute just means there's a newer/better method in place - not that the existing method is broken.
Cheers, Lee.
Makes total sense... thanks for all your insight! Love this community!
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.