Awesome! Could you let me know when the NuGet package is available for the official release? Can I use the test version by just replacing the dll's, or does this version contain other changes as well?
There is a new test version that fixes the issue Markus has as well. I have refactored the complete core database access now and all is using Applicationcontext.Database now instead of SqlHelper
@Richard Looks like the issue with the SqlHelper is gone. The number of connections are not growing like before.
But the issue on the "Validation Issues"-page is still there. I'm not searching or anything, just getting this error when pressing the "Validation Issues" node in the tree:
Server Error in '/' Application.
Object must implement IConvertible.
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.InvalidCastException: Object must implement IConvertible.
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:
[InvalidCastException: Object must implement IConvertible.]
System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) +13956569
petapocofactory75(IDataReader ) +1298
Umbraco.Core.Persistence.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1055.0
Starnge works on my machine would it be possible to send me the data of SEOCheckerValidationIssues table best to mail [email protected]. i will look into this tomorrow but i think data is causing the issue.
This can be easily solved by allowing MARS in your connection string. Add MultipleActiveResultSets=true to the provider part of your connection string (where Data Source, Initial Catalog, etc. are specified).
E.g. <add name="umbracoDbDSN" connectionString="server=SERVER;database=DBName;user id=sa;password=XXXXX;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />
Hmm... I would not say that this would solve the problem. It's like "Swipe the dust under the bed" - closing the connection to the db in the calling code is the right solution - adding MARS is just a way to "hack" around it.
Any way - if you are using the latest version of Seo Checker you're safe.
@Markus & @Arjan, I agree with you both. However, in case someone is leveraging some other plugin and you don't have latest fixes available from them then implement config fix make scene.
SEO Checker has already fix implemented. So, we should use latest version. :) I added that comments because I noticed issue with some other plugins.
There is already an open DataReader associated with this Command which must be closed first.
Hi guys,
I ran into a problem after upgrading Umbraco to 7.6.0 version.
http://prntscr.com/f40ta2
Seochecker 1.9.4.1
Thanks, Mike
Hi Mike,
This is because Umbraco 7.6.0 causes an issue with the lecacy documenttype object.
I am currently on holiday but will create a fix next week that removes all legacy functionality and will use the service api's only.
This will mean that 1.10.x will no longer support older versions of Umbraco.
Sorry for the hassle.
Best,
Richard
Ran into the same issue with SEO Checker 1.9.4.1 on Umbraco 7.6.1. Looking forward to version 1.10.x.
Hi Arjan,
Jope to have a test version ready by tomorrow.
Best,
Richard
If you download v 1.10.0 test version here the issue should be gone. Official release next week.
Hope this helps.
Awesome! Could you let me know when the NuGet package is available for the official release? Can I use the test version by just replacing the dll's, or does this version contain other changes as well?
I think dll's replacing is enough and best to keep an eye on twitter or SEOChecker release page.
Perfect! Thanks.
Hi!
The issue with commands dissapeared after the upgrade, but having an problems with the "Validation Issues"-option. Getting:
Any particular search you did or just opened since that works over here. What version are you on Markus?
Best,
Richard
Umb: 7.6.1, Seo Checker: The version you posted a file to earlier in this thread.
There is a new test version that fixes the issue Markus has as well. I have refactored the complete core database access now and all is using Applicationcontext.Database now instead of SqlHelper
Download here
Hope this works better.
Best,
Richard
@Richard Looks like the issue with the SqlHelper is gone. The number of connections are not growing like before.
But the issue on the "Validation Issues"-page is still there. I'm not searching or anything, just getting this error when pressing the "Validation Issues" node in the tree:
Server Error in '/' Application.
Object must implement IConvertible.
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.InvalidCastException: Object must implement IConvertible.
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:
[InvalidCastException: Object must implement IConvertible.] System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) +13956569 petapocofactory75(IDataReader ) +1298 Umbraco.Core.Persistence.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1055.0
This version works like a charm on Umbraco 7.6.1. Could you notify us here once it's available on NuGet?
Hi Markus,
Starnge works on my machine would it be possible to send me the data of SEOCheckerValidationIssues table best to mail [email protected]. i will look into this tomorrow but i think data is causing the issue.
Best,
Richard
I've sent the data, clearing the table did remove the error - let's see if it comes back =D
Thanks for great support / work during the last days Richard!
// m
I've just released version 1.10.0. The official release that fixes this issue.
This can be easily solved by allowing MARS in your connection string. Add MultipleActiveResultSets=true to the provider part of your connection string (where Data Source, Initial Catalog, etc. are specified).
E.g. <add name="umbracoDbDSN" connectionString="server=SERVER;database=DBName;user id=sa;password=XXXXX;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />
Hmm... I would not say that this would solve the problem. It's like "Swipe the dust under the bed" - closing the connection to the db in the calling code is the right solution - adding MARS is just a way to "hack" around it.
Any way - if you are using the latest version of Seo Checker you're safe.
// m
@Markus: My thoughts exactly.
@Markus & @Arjan, I agree with you both. However, in case someone is leveraging some other plugin and you don't have latest fixes available from them then implement config fix make scene.
SEO Checker has already fix implemented. So, we should use latest version. :) I added that comments because I noticed issue with some other plugins.
Yes, in that case you could use MARS as a TEMPORARY fix, until the package creator implements a proper fix.
is working on a reply...