I succesfully installed the link checker and was using it (great package by the way!) but all of a sudden it has stopped working? When i click on the Check Links button it is not doing anything: not firing, no errors, nothing.
Mmmm, it's a difficult one to diagnose if it just flat stops working. Has anything changed about your site, such as changes to web.config or hosting, that you can think coincided with this?
One thing you can do is check the umbracoLog table in the database and look for any exceptions in the "Error" category. If there are, let me know and I'll try and interpret.
That is definitely odd! Doesn't make any sense to me at all, though I guess it could be part of the problem with web-forms where there is only one form and one control fires validation on another. I'll try and remember to update it to put that in. Thanks for your input!
Still have same problem. And I know it only happens when uBlogsy is installed. Disabling CausesValidation indeed helped. uBlogsy breaking not just your addon, it also breaks 301 url tracker data type.
With or without uBlogsy, LinkChecker doesn't work. Even when Start Link Check button can be pressed, it founds no links. Even on empty Umbraco from webmatrix, with simple starter kit. Try it yourself. (iis8, sql server 2008, webmatrix, chrome, but I don't think it matters)
Would love to get this package to work. It's really must-have.
System.IO.FileLoadException: Could not load file or assembly 'HtmlAgilityPack, Version=1.3.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'HtmlAgilityPack, Version=1.3.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' at Diplo.LinkChecker.LinkParser.GetLinksInHtml(String html) at Diplo.LinkChecker.Checker.CheckPages(IEnumerable`1 pagesToCheck, Int32 totalPagesToCheck) at Diplo.LinkChecker.Checker.CheckUmbracoPages(Uri baseUrl, Int32 nodeId) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Current HtmlAgilityPack version here is 1.4.5.0 (instead of 1.3.0.0), I think I know what's going wrong. Still need your help updating package, I think.
Thanks, Dimps, you are correct - it must be because they have updated the version of the HtmlAgility pack in the latest Umbraco release. Unfortuanetly I haven't had much time to work on this package due to becoming a new Dad - a newborn baby leaves you with little free time :) But I'll try and update it ASAP.
OK, thankfully updating the package to work with 4.9 was just a case of updating the references it compiles against. Therefore I've released version 1.5 which should now work OK with Umbraco 4.8 and above.
Thank you, now it works. (after I add CausesValidation="False" to start check button; I'll also try to file this bug to uBlogsy, you may add it by default to your package, if you know it breaks nothing)
Thanks, Dimps, I've also added the CausesValidation=False to the button as you suggested. It shouldn't cause any problems as the control doesn't use asp.net validators. I guess other package authors need to remember to use unique validation groups for their controls.
Checker stopped working?
Hi,
I succesfully installed the link checker and was using it (great package by the way!) but all of a sudden it has stopped working? When i click on the Check Links button it is not doing anything: not firing, no errors, nothing.
Any ideas would be most welcomed!
Thanks
Kenny
Hi,
Mmmm, it's a difficult one to diagnose if it just flat stops working. Has anything changed about your site, such as changes to web.config or hosting, that you can think coincided with this?
One thing you can do is check the umbracoLog table in the database and look for any exceptions in the "Error" category. If there are, let me know and I'll try and interpret.
HI Dan,
I revisited this and when i looked at LinkChecker.ascx i came across an article that said to put CausesValidation in to the button.
<asp:Button ID="ButtonStartCheck" CausesValidation="false" runat="server" Text="Start Link Check" CssClass="button" ToolTip="Click to check links" OnClick="ButtonStartCheck_Click" />
I tried this and it seemed to work? Odd!
Kenny
That is definitely odd! Doesn't make any sense to me at all, though I guess it could be part of the problem with web-forms where there is only one form and one control fires validation on another. I'll try and remember to update it to put that in. Thanks for your input!
Still have same problem. And I know it only happens when uBlogsy is installed. Disabling CausesValidation indeed helped. uBlogsy breaking not just your addon, it also breaks 301 url tracker data type.
System.IO.FileLoadException: Could not load file or assembly 'HtmlAgilityPack, Version=1.3.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'HtmlAgilityPack, Version=1.3.0.0, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' at Diplo.LinkChecker.LinkParser.GetLinksInHtml(String html) at Diplo.LinkChecker.Checker.CheckPages(IEnumerable`1 pagesToCheck, Int32 totalPagesToCheck) at Diplo.LinkChecker.Checker.CheckUmbracoPages(Uri baseUrl, Int32 nodeId) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Current HtmlAgilityPack version here is 1.4.5.0 (instead of 1.3.0.0), I think I know what's going wrong. Still need your help updating package, I think.
Thanks, Dimps, you are correct - it must be because they have updated the version of the HtmlAgility pack in the latest Umbraco release. Unfortuanetly I haven't had much time to work on this package due to becoming a new Dad - a newborn baby leaves you with little free time :) But I'll try and update it ASAP.
OK, thankfully updating the package to work with 4.9 was just a case of updating the references it compiles against. Therefore I've released version 1.5 which should now work OK with Umbraco 4.8 and above.
Thank you, now it works. (after I add CausesValidation="False" to start check button; I'll also try to file this bug to uBlogsy, you may add it by default to your package, if you know it breaks nothing)
Thanks, Dimps, I've also added the CausesValidation=False to the button as you suggested. It shouldn't cause any problems as the control doesn't use asp.net validators. I guess other package authors need to remember to use unique validation groups for their controls.
is working on a reply...