Trying to get my head around using SEO Checker 2.0.1 and having trouble importing either a csv or an xslx file. Throws several console errors, all circulating around the following:
Cannot read property 'length' of null
Contents of log:
2018-08-29 12:38:31,161 [P18732/D3/T15] ERROR SEOChecker.Controllers.Dialogs.Redirects.ImportRedirectsDialogApiController - Unhandled controller exception occurred
System.ArgumentNullException: Value cannot be null.
Parameter name: response
at System.Net.Http.HttpResponseMessageExtensions.TryGetContentValue[T](HttpResponseMessage response, T& value)
at SEOChecker.UI.Attributes.SEOCheckerController.OnActionExecuted(HttpActionExecutedContext actionExecutedContext)
at System.Web.Http.Filters.ActionFilterAttribute.OnActionExecutedAsync(HttpActionExecutedContext actionExecutedContext, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()
Im using Google Sheets, exporting the sheet out as either a csv or an xslx file and uploading this using the 'Import Redirects' option within the 'Redirect manager' section.
Installed a clean, fresh version of 7.12.1, added SEO Checker 2.0.1 and licence file to hopefully rule out anything ive done in my main installation and unfortunately the same console errors are shown.
Figured it out, it looks like the there is a minimum upload limit, take the following as an example
Two files, both containing the same data, exported out from google sheets as the following file types
A = csv file
Size: 30bytes
Size on disc: 0bytes
B = xsls file
Size: 3.65 KB
Size on disc: 4.00 KB
SEO Checker upload didnt accept any, both throw the console errors you see above.
Made a new file, C, filled this with a lot more data:
Size: 27 KB
Size on disc: 32 KB
SEO Checker accepted this, so there must be a minimum file size on upload, somewhere between 4 and 32KB hopefully this helps someone out there experiencing an upload problem.
Javascript console errors on file import
Trying to get my head around using SEO Checker 2.0.1 and having trouble importing either a csv or an xslx file. Throws several console errors, all circulating around the following:
Contents of log:
Im using Google Sheets, exporting the sheet out as either a csv or an xslx file and uploading this using the 'Import Redirects' option within the 'Redirect manager' section.
Thanks for any help you are able to offer.
Update:
Installed a clean, fresh version of 7.12.1, added SEO Checker 2.0.1 and licence file to hopefully rule out anything ive done in my main installation and unfortunately the same console errors are shown.
Could this be an incompatibility with 7.12.1?
Figured it out, it looks like the there is a minimum upload limit, take the following as an example
Two files, both containing the same data, exported out from google sheets as the following file types
A = csv file Size: 30bytes Size on disc: 0bytes
B = xsls file Size: 3.65 KB Size on disc: 4.00 KB
SEO Checker upload didnt accept any, both throw the console errors you see above.
Made a new file, C, filled this with a lot more data: Size: 27 KB Size on disc: 32 KB
SEO Checker accepted this, so there must be a minimum file size on upload, somewhere between 4 and 32KB hopefully this helps someone out there experiencing an upload problem.
Hi,
The excel component might throw the error. make sure you are using No formatting in the xlsx file.
I add better error reporting on this in a future release.
Best,
Richard
is working on a reply...