| View previous topic :: View next topic |
| Author |
Message |
Kairos
Joined: 15 Oct 2008
Posts: 20
|
 Posted: Thu Dec 25, 2008 3:02 pm Post subject: [beta9] Filter "Ignore whole content filtered" ... |
 |
|
[beta 9] Filter "Ignore whole content filtered" does not work.
Hallo,
I use Beta 7 and 9 since some days and found a bug by monitoring Google date range. Example:
http://www.google.com/search?hl=en&safe=off&q=test123+for+Website+Watcher&as_qdr=d&btnG=Search
(With Google date range you can watch new indexed websites to specific keywords or phrases.)
I use this filter:
StartToRegex(Tip\: Save time by hitting the return key instead of clicking on "search")
Your search - test123 for Website Watcher - did not match any documents.*
With this filter the whole content is filtered if there is the message by Google: "Your search - test123 for Website Watcher - did not match any documents."
Additional I set "Ignore Message 'whole content filtered'" at Check (1).
In WSW 4.42 it works fine. If there is no new indexed website at google, I get no alert by WSW. Now with beta 9 (and 7) there is the persistent error message "Warning. Whole content filtered" (although I set "Ignore whole content filtered").
You can download the example-bookmark here: www.kleingewerbe.info/deepweb/wsw.zip
(Sorry for my bad english.) |
|
| Back to top |
|
 |
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Mon Dec 29, 2008 1:49 pm Post subject: |
|
|
| Quote: | I use this filter:
StartToRegex(Tip\: Save time by hitting the return key instead of clicking on "search")
Your search - test123 for Website Watcher - did not match any documents.*
|
I cannot reproduce it here, the text Tip: Save time by hitting the return key instead of clicking on "search" isn't available when I open such a page.
| Quote: | With this filter the whole content is filtered if there is the message by Google: "Your search - test123 for Website Watcher - did not match any documents."
Additional I set "Ignore Message 'whole content filtered'" at Check (1).
|
From what I understand I think that in your case you should use the "Ignore update" feature.
1. Open bookmark properties
2. Select the "Advanced" tab
3. Select "Ignore updates" on the left side
4. Enter the the text: - did not match any documents.
| Quote: | | In WSW 4.42 it works fine. |
I think it "worked" fine, but this page was changed somehow and the first filter definition no longer has matches. As a result, your filter no longer matches the whole content.
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Mon Dec 29, 2008 7:19 pm Post subject: |
|
|
| Martin Aignesberger wrote: | From what I understand I think that in your case you should use the "Ignore update" feature.
1. Open bookmark properties
2. Select the "Advanced" tab
3. Select "Ignore updates" on the left side
4. Enter the the text: - did not match any documents.
|
 Thanks for this tip! I think this could work. (I test it tomorrow.)
| Martin Aignesberger wrote: | | I cannot reproduce it here, the text Tip: Save time by hitting the return key instead of clicking on "search" isn't available when I open such a page. |
If you open the link in Internet Explorer (and WSW) instead in Firefox you can see it. But that is not so important to solve the problem with Google.
Please note:
Your tip with "Ignore updates" could work as an good alternative but I'm sure there is a bug. My filter ...
| Code: | StartToRegex(Tip\: Save time by hitting the return key instead of clicking on "search")
Your search - test123 for Website Watcher - did not match any documents.* |
works fine. With it, the whole content is filtered if Google Daterange found no new indexed websites for "test123 for Website Watcher". (This is good, I want this so.)
And although I additional set "Ignore Message 'whole content filtered'" at Check (1) there comes the error message "Warning. Whole content filtered" (see my wsw.zip). This is a bug, because I want filtering the whole content at this specific situation. I don't want this alert.
You can test this if you watch my example, set my filter and wait for one or two days.
(Sorry for my bad english.)  |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Thu Jan 01, 2009 1:20 pm Post subject: |
|
|
| Martin Aignesberger wrote: | ... use the "Ignore update" feature.
1. Open bookmark properties
2. Select the "Advanced" tab
3. Select "Ignore updates" on the left side
4. Enter the the text: - did not match any documents.
|
With this I get tons of useless alerts too. See example:
http://www.kleingewerbe.info/deepweb/stupid-alert.jpg
I don't need this alert. What is the sence of "Ignore update" if WSW shows me this error message like an real alert für a changed bookmark? 
PS: It's the same problem as the error message in my first post in this thread. |
|
| Back to top |
|
|
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Fri Jan 02, 2009 9:44 am Post subject: |
|
|
| Quote: | | If you open the link in Internet Explorer (and WSW) instead in Firefox you can see it. |
Hmm, I'm not able to see this text in IE or in WSW. 
Could you please post a screenshot where I can see this text?
This error is caused by the configuration "Alert update after XX errors in series" which can be configured in the program configuration ("Check" tab). Seems that you use a value of 1.
But the "Ignore update" feature should probably not be affected by this configuration (which was not the case in v4). The next version will revert to the old v4 behavior, then my suggested solution will work, too.
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Tue Jan 06, 2009 4:47 pm Post subject: |
|
|
Hello,
I am back to annoying you. 
| Martin Aignesberger wrote: | | Quote: | | If you open the link in Internet Explorer (and WSW) instead in Firefox you can see it. |
Hmm, I'm not able to see this text in IE or in WSW.
Could you please post a screenshot where I can see this text? |
www.kleingewerbe.info/deepweb/wsw-screenshot01.gif
www.kleingewerbe.info/deepweb/wsw-screenshot02.gif
| Martin Aignesberger wrote: | This error is caused by the configuration "Alert update after XX errors in series" which can be configured in the program configuration ("Check" tab). Seems that you use a value of 1.
|
Yes I do, but what means "error"? I thought a value of 1 alerts me, if a website is not reachable. This error is only at my Google-Bookmarks when the whole content is filtered (or if the "Ignore update"-Feature is used). It's very strange. And please note: Google is always reachable, they have 50.000 Server or so. |
|
| Back to top |
|
|
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Wed Jan 07, 2009 9:40 am Post subject: |
|
|
| Quote: | | Yes I do, but what means "error"? I thought a value of 1 alerts me, if a website is not reachable. |
Yes, this "whole content filtered" is also handled as normal error although you prevent that error message in the bookmark properties.
Strange, I still cannot see this text!!
Anyway, I think I could solve this problem.
Please contact me via our ticket system, then I'll send you an internal beta for testing. Both solutions should work then...
http://www.aignes.com/email.htm
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Fri Jan 09, 2009 9:24 am Post subject: |
|
|
| Quote: | | Please contact me via our ticket system, then I'll send you an internal beta for testing. Both solutions should work then... |
I have bad news and I have good news. First the bad news:
This beta is horrible.  Many errors and many timeouts at different bookmarks - and the strange thing: some Google-Bookmarks work, other do not work, although they have the same configuration and filters.
The good news: I found a solution to solve the most problems. 
I changed the "Technology to check websites" at Check(1) from "Standard" to "Internet Explorer" and everything works fine. The Google-Bookmarks too - in both solutions ("Ignore update" and "Ignore 'whole content is filtered'").
Here are some websites which not work in beta 9c AND Technology "Standard" for you to test:
(*) = (Status-Message)
http://www.juraforum.de/forum/f71/s (Timeout)
(With Techn. "Internet Explorer" it works but the check is very slow, it needs 5 min. or so to check this site.)
http://forum.zingel.de/viewforum.php?f=3 (Timeout)
http://www.google.de/search?hl=de&safe=off&q=inurl%3Aemoji+site%3A.jp+-unicode&as_qdr=d&btnG=Suche&meta=&aq=f&oq= (Error) |
|
| Back to top |
|
|
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Fri Jan 09, 2009 12:18 pm Post subject: |
|
|
| Quote: | I have bad news and I have good news. First the bad news:
This beta is horrible. Many errors and many timeouts at different bookmarks - and the strange thing: some Google-Bookmarks work, other do not work, although they have the same configuration and filters.
|
Hmm, this must be a (temporary) problem on your end.
But could you please send me a bookmark that takes tooo long? Then I can try it with your configuration and analyze your log file to see if there is a bottleneck within WSW.
1. Right click a bookmark
2. Select "Organize" + "Export to WebSite-Watcher export file (*.zip)"
3. Save the file and attach it to your ticket/e-mail - http://www.aignes.com/email.htm
4. Paste the URL of that thread into the ticket/e-mail.
| Quote: | | in both solutions ("Ignore update" and "Ignore 'whole content is filtered'"). |
Great. Thanks for the info.
All three URLs work without a problem here, I could check them within a single second. Please send me these three bookmarks, probably you have a specific configuration that causes a problem.
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Fri Jan 09, 2009 2:47 pm Post subject: |
|
|
| Quote: | | But could you please send me a bookmark that takes tooo long? Then I can try it with your configuration and analyze your log file to see if there is a bottleneck within WSW. |
http://www.kleingewerbe.info/deepweb/wsw-juraforum-5min-to-check.zip
See the Log-File. It starts at 09:53 am and ends at 09:58 am - thats 5 min to check.
Now, a second check at 02:40 pm. The same problem, at this time it needs 9 min to check:
http://www.kleingewerbe.info/deepweb/wsw-juraforum-9min-to-check.zip
Please note: With Technology "Standard" it doesn't work at all, with Technology "Internet Explorer" it needs 5 to 9 min.
Next check at 02:56 pm, at this time with Technologie "Standard". It produces only an 'Error', the big problem of beta 9c. See here:
http://www.kleingewerbe.info/deepweb/wsw-juraforum-error.zip
Next check at 03:07 pm, back to Technology "Internet Explorer". Now it takes only seconds to check. 
http://www.kleingewerbe.info/deepweb/wsw-juraforum-seconds-to-check.zip
Next ... back to Tech. "Standard" ... error, back to Tech. "Internet Explorer" ... works fine.
Strange adventures with WSW.
| Quote: | | All three URLs work without a problem here, I could check them within a single second. Please send me these three bookmarks, probably you have a specific configuration that causes a problem. |
First URL, see above. The same behavior with forum.zingel.de:
Tech. "Standard": Timeout; see here:
http://www.kleingewerbe.info/deepweb/wsw-zingel-timeout.zip
Tech. "Internet Explorer": works fine; see here:
http://www.kleingewerbe.info/deepweb/wsw-zingel-iexplorer.zip
And last, but not least my Google-Example-Bookmark with Tech. "Standard": error, see here:
http://www.kleingewerbe.info/deepweb/wsw-google-error.zip
And with Tech. "Internet Explorer: works fine, see here:
http://www.kleingewerbe.info/deepweb/wsw-google-iexplorer.zip
Conclusion for Friday: WSW is a fine tool, but a littly buggy today.  |
|
| Back to top |
|
|
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Fri Jan 09, 2009 3:34 pm Post subject: |
|
|
| Quote: | | Conclusion for Friday: WSW is a fine tool, but a littly buggy today. |
I have tested all these bookmarks here, and they work fast and without a problem. Seems that something is wrong on your end.
Do you probably use a Firewall, a proxy or another Internet Security Software that could block or extremely slow down WebSite-Watcher? If not, does a Windows restart solve this issue? I cannot reproduce these problems here nor do we have similar reports from other users...
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Fri Jan 09, 2009 6:15 pm Post subject: |
|
|
| Quote: | | Do you probably use a Firewall, a proxy or another Internet Security Software that could block or extremely slow down WebSite-Watcher? |
Firewall: yes, but that's no problem. Proxy or another Internet Security Software: no.
| Quote: | | If not, does a Windows restart solve this issue? |
Yes.
Now I can say: everything works fine I tested all bookmarks - no problems. Importend: The option "Ignore update" works very fine now (no useless alerts).
I have no idea why a Windows restart solves the problems of WSW from today. I checked yesterday all my bookmarks with beta 9 and changed then to beta 9c. Today in the morning (my PC was on overnight), AutoWatch starts and the problems had begun. |
|
| Back to top |
|
|
Kairos
Joined: 15 Oct 2008
Posts: 20
|
| Posted: Sat Jan 31, 2009 4:06 am Post subject: |
|
|
| Martin Aignesberger wrote: | | But the "Ignore update" feature should probably not be affected by this configuration (which was not the case in v4). The next version will revert to the old v4 behavior, then my suggested solution will work, too. |
The bug is still there (beta 5.0.1 beta-2). I get sometimes useless alerts by using "Ignore update". See screenshots:
http://www.kleingewerbe.info/x/tmp/wsw01.gif
http://www.kleingewerbe.info/x/tmp/wsw02.gif
Bookmark of second screenshot (wsw02.gif):
http://www.kleingewerbe.info/x/tmp/wsw-ignore-update-fail.zip
-------------------------------------------------------------------------
*Update*
Wait, I think that I understand the problem now. It's not a bug, it's only a confusing behavior of WSW. Let me explain it by the example of the wsw02-screenshot:
29.01.2009:
WSW founds correctly an change on the website but I had no time to check this.
30.01.2009:
The bookmark is still marked as unread and WSW checks the bookmark again because the autowatch is 24 hours for it. Now WSW founds the text for "ignore update".
31.01.2009:
I had time to check all my bookmarks. The changed bookmark of 29.01.2009 is still marked as unread. I click on it and WSW shows me the error-message (wsw02-screenshot) of 30.01.2009 for "ignore update". And this is the wrong behavior of WSW! It has to show me the old version of 29.01.2009 (with the real changes at the website)!
I hope my explaination was understandable. |
|
| Back to top |
|
|
Martin Aignesberger
Site Admin
Joined: 11 May 2005
Posts: 4880
|
| Posted: Sat Jan 31, 2009 10:08 am Post subject: |
|
|
| Quote: | | I hope my explaination was understandable. |
yes, and thanks for figuring that out. You're right, it's an incorrect behavior that should be fixed. It's on my list for version 5.1.0 now.
_________________
Martin Aignesberger [SUPPORT] |
|
| Back to top |
|
|
|
FAQ
Search
Register
Profile
Log in
