We are getting alot of errors on Umbraco Cloud that state SeoChecker cant convert DB values to editor values.
Message:
SEOChecker: SEOChecker: Error converting DB values to editor values
Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at SEOChecker.Core.Umbraco.DocumentWrappers.UmbracoDocument..ctor(IContent doc, IContextInfo info, String culture, String segment)
at SEOChecker.Core.Repository.Umbraco.UmbracoDocumentRepository.Single(Int32 id, IContextInfo context, String culture, String segment)
at SEOChecker.DataTypes.PropertyEditors.PropertyEditorWrappers.SEOCheckerPropertyWrapper.ToEditor(Property property, IDataTypeService dataTypeService, String culture, String segment)
On this site we do not run any background process. And we do not get any visual errors when trying to edit in backoffice. But it shows up in the log files.
Could it have anything to do with it running in trial mode?
I also get this error in the logs and I have been able to reproduce it. When i open a page that is in the recycle bin SEO-checker logs 6 errors to the log for me.
I hope that will be a hint of how to reproduce it and fix it.
I can reproduce it indeed. If the fix is simple it will be in the 2.9 release otherwise a release after that one. Don't open Items in the Trash can ;-)
When i view a document in Umbraco that uses SeoChecker, then i get this Error 3 times in a row: When i save the document i get the same error again 2 times in a row.
System.ArgumentNullException: Value cannot be null.
Parameternavn: Cannot find a content type with alias
ved SEOChecker.Core.Repository.Definition.DefinitionFactory.Single(String alias)
ved SEOChecker.Core.Config.Configuration.GetDocumentTypeByAlias(String alias, String doctypeAlias)
ved SEOChecker.Core.Config.Configuration.GetDocumentTypeByAlias(String alias)
ved SEOChecker.Core.Umbraco.DocumentWrappers.UmbracoDocument.get_SEOConfiguration()
ved SEOChecker.Core.Extensions.UmbracoDocumentExtensions.GetDefaultTitlePropertyValue(IUmbracoDocument doc, String culture, String segment)
ved SEOChecker.DataTypes.Model.SEOCheckerModel..ctor(SEOCheckerValues value, IUmbracoDocument document, SEOCheckerDataTypeConfig datatypeConfig, String culture, String segment)
ved SEOChecker.DataTypes.PropertyEditors.PropertyEditorWrappers.SEOCheckerPropertyWrapper.ToEditor(Property property, IDataTypeService dataTypeService, String culture, String segment)
Ok the last is not a SEO Checker error and great find Now I can reproduce as well. Will fix ASAP. Was better to have a new topic by the way since this was related to a total different issue.
I have a issue with the social media previewer.
On one of my doctypes the fallback image works, but not on the other doctypes ?... There the image placeholder are just blank, unless I select a image in the social media field.
"SEOChecker: SEOChecker: Error converting DB values to editor values"
System.NullReferenceException: The object reference is not set to an instance of an object. by SEOChecker.Library.MetaData..ctor (Int32 id, String culture, String segment) by SEOChecker.DataTypes.Model.SEOCheckerSocialModel..ctor (SEOCheckerSocialValues value, IUmbracoDocument document, SEOCheckerSocialDataTypeConfig Statring.DonTypeConfig datatypeConfig .PropertyEditors.PropertyEditorWrappers.SEOCheckerSocialPropertyEditorWrapper.ToEditor (Property property, IDataTypeService dataTypeService, String culture, String segment)
Ah ok, That si almost the same error but on a different property editor. Makes sense now. This one was on the list to fix but need some time to check it. Seems that something is accessing the property editor without httpcontext. Will come back to this but is a nasty one to fix,
The mentioned hotfix https://www.dropbox.com/s/g1jrjdsu47adttj/seo-checker29_1.zip?dl=0 seems does fixes the Error converting DB values to editor values issue, but it does produce more Error in UrlRewriteComponent for url rewriting
Exception error. More, because this issue has already existed for a long time. I believe this is by calls to the scheduled api /umbraco/seochecker/seocheckerscheduleapi/run, unfortunately no way to disable it.
SEOChecker: SEOChecker: Error in UrlRewriteComponent for url rewriting
Exception
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.List1.Enumerator.MoveNextRare()
at System.Collections.Generic.List1.Enumerator.MoveNext()
at SEOChecker.Core.Providers.UrlProviders.UrlRewriteProviders.RewriteUrl(String url, UrlRewriteConfig config)
at SEOChecker.Core.Components.UrlRewriteComponent.App_BeginRequest(Object sender, EventArgs e)
I just marked 3000 SEO Checker errors as read on Umbraco Cloud :-(
Updated to 2.9.1 but still getting alot of these errors:
Message:
SEOChecker: SEOChecker: Error converting DB values to editor values
Exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at SEOChecker.Library.MetaData..ctor(Int32 id, String culture, String segment)
at SEOChecker.DataTypes.Model.SEOCheckerSocialModel..ctor(SEOCheckerSocialValues value, IUmbracoDocument document, SEOCheckerSocialDataTypeConfig datatypeConfig, String culture, String segment)
at SEOChecker.DataTypes.PropertyEditors.PropertyEditorWrappers.SEOCheckerSocialPropertyEditorWrapper.ToEditor(Property property, IDataTypeService dataTypeService, String culture, String segment)
A fix (released on NuGet) would be nice and about time, sorry to put it like this.
So this isn't getting addressed at all? Is SEO Checker still maintained Richard? I'd like to know before we start buying licences as you'll understand.
Yup It's maintained in fact it is in current Sprint. Can only do one thing at the time Stefan. The fact Umbraco V8 released to soon last year and Corona didn't help either...
I have send a test version to Stefan last week and the errors were gone. You can also use this hotfix version for now. In 2.10 this fix will be included as well.
Error converting DB values to editor values
Hi.
Running Umbraco Cloud 8.1.4 and SeoChecker 2.8.2
We are getting alot of errors on Umbraco Cloud that state SeoChecker cant convert DB values to editor values.
HI Bo,
Do you get these in the editor as well or are you running some sort of background process?
Best,
Richard
Hi Richard.
Thanks for replying.
On this site we do not run any background process. And we do not get any visual errors when trying to edit in backoffice. But it shows up in the log files.
Could it have anything to do with it running in trial mode?
Dont' think that should matter but if you mail [email protected] I will send you a trial license.
Best,
Richard
We had a trial license on and changed it to a real one, but we still have the same issue.
We are trying to find out when the problem occours, but we cant seem to trigger it, it just shows up in the log.
I also get this error in the logs and I have been able to reproduce it. When i open a page that is in the recycle bin SEO-checker logs 6 errors to the log for me.
I hope that will be a hint of how to reproduce it and fix it.
Great find,
I can reproduce it indeed. If the fix is simple it will be in the 2.9 release otherwise a release after that one. Don't open Items in the Trash can ;-)
Thanks for getting back,
Richard
Hi Richard.
Did you ever found a solution to this?
I installed version 2.9.0 on a Umbraco 8.5.1 cloud website.
An again i get alot of these errors.
Hi Bo,
It was related to items that were in the recycle bin. But that is fixed. What is the error?
Best,
Richard
When i view a document in Umbraco that uses SeoChecker, then i get this Error 3 times in a row: When i save the document i get the same error again 2 times in a row.
As a bonus info. The document i tried this on was not published, only saved.
When i try to do a schedule publish i get this debug info, that leads to a 404 error.
Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:7579/umbraco/backoffice/UmbracoApi/Content/PostSave
Ok the last is not a SEO Checker error and great find Now I can reproduce as well. Will fix ASAP. Was better to have a new topic by the way since this was related to a total different issue.
Best,
Richard
I should maybe have created a new topic. But i did not want to have 2 unfinished topics with the same name.
But great that you can reproduce, so you can try fix it.
Yes the last is only a debug info. But i was wondering why SeoChecker is calling http://localhost:7579/umbraco/backoffice/UmbracoApi/Content/PostSave when i try to do a schedule publish?
Ok but the other issue was solved in 2.9.
Hi Richard.
When you have a fix for it, please post it, then i mark it as the correct answer :)
I will create a new bug report for the debug info from the SEOChecker.Core.Components.UrlRedirectComponent.
Hi Bo,
Think a side effect of another fix fixed this issue as well, could not reproduce it anomore with fix below. but can with 2.9.0
https://www.dropbox.com/s/jszoolorc4rywyk/seo-checker29_1.zip?dl=0
Hey Richard,
I'm still getting a lot of error in the log
"SEOChecker: SEOChecker: Error converting DB values to editor values"
running 8.5.4 and Seochecker 2.9.0
Hi Thomas,
Use this hotfix please.
https://www.dropbox.com/s/g1jrjdsu47adttj/seo-checker29_1.zip?dl=0
Hope this helps,
Richard
Thanks I have just tried that. :)
I have a issue with the social media previewer. On one of my doctypes the fallback image works, but not on the other doctypes ?... There the image placeholder are just blank, unless I select a image in the social media field.
Different Image type maybe? The picker checks the datatype to determine if something is a picker.
hmm have tried with the same image on diffrent doctype. It only works on one of them..
Also, I have added the hotfix. still getting the log error:
"SEOChecker: SEOChecker: Error converting DB values to editor values"
Only on the item that is not having the image picker I assume? Any other errors related to this in the log?
Both doctypes have the same composition.
With the same Image picker / alias.
In Seochecker both doctype in social have the same picker..
"SEOChecker: SEOChecker: Error converting DB values to editor values"
System.NullReferenceException: The object reference is not set to an instance of an object. by SEOChecker.Library.MetaData..ctor (Int32 id, String culture, String segment) by SEOChecker.DataTypes.Model.SEOCheckerSocialModel..ctor (SEOCheckerSocialValues value, IUmbracoDocument document, SEOCheckerSocialDataTypeConfig Statring.DonTypeConfig datatypeConfig .PropertyEditors.PropertyEditorWrappers.SEOCheckerSocialPropertyEditorWrapper.ToEditor (Property property, IDataTypeService dataTypeService, String culture, String segment)
Ah ok, That si almost the same error but on a different property editor. Makes sense now. This one was on the list to fix but need some time to check it. Seems that something is accessing the property editor without httpcontext. Will come back to this but is a nasty one to fix,
Cool :) Thanks
having the same issue here
The mentioned hotfix https://www.dropbox.com/s/g1jrjdsu47adttj/seo-checker29_1.zip?dl=0 seems does fixes the Error converting DB values to editor values issue, but it does produce more Error in UrlRewriteComponent for url rewriting Exception error. More, because this issue has already existed for a long time. I believe this is by calls to the scheduled api /umbraco/seochecker/seocheckerscheduleapi/run, unfortunately no way to disable it.
SEOChecker: SEOChecker: Error in UrlRewriteComponent for url rewriting Exception System.InvalidOperationException: Collection was modified; enumeration operation may not execute. at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource) at System.Collections.Generic.List
1.Enumerator.MoveNextRare() at System.Collections.Generic.List
1.Enumerator.MoveNext() at SEOChecker.Core.Providers.UrlProviders.UrlRewriteProviders.RewriteUrl(String url, UrlRewriteConfig config) at SEOChecker.Core.Components.UrlRewriteComponent.App_BeginRequest(Object sender, EventArgs e)I just marked 3000 SEO Checker errors as read on Umbraco Cloud :-( Updated to 2.9.1 but still getting alot of these errors:
A fix (released on NuGet) would be nice and about time, sorry to put it like this.
I Think there is an issues with Umbraco Cloud and the HttppContext to, mayeb they do something on a background thread that causes this on Cloud.
Looking at the lines where the exception is thrown:
It wouldn't hurt adding simple null checks for
ContextHelper.UmbracoHelper
andpublishedContent
, right? I guess one of those isnull
.So this isn't getting addressed at all? Is SEO Checker still maintained Richard? I'd like to know before we start buying licences as you'll understand.
Hi Stefan,
Yup It's maintained in fact it is in current Sprint. Can only do one thing at the time Stefan. The fact Umbraco V8 released to soon last year and Corona didn't help either...
Best,
Richard
I know but it would be nice to keep us posted somehow. We can't guess what's happening, right?
Yup that's true and agree it took too long.
Hi All,
I have send a test version to Stefan last week and the errors were gone. You can also use this hotfix version for now. In 2.10 this fix will be included as well.
Hope this helps for now,
Richard
is working on a reply...