Kommentare für svenkubiak http://www.svenkubiak.de Kleines, feines Blog zu unterschiedlichen Themen. Sun, 22 Jan 2012 15:59:18 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Kommentar zu Von Spiegeltreibern werden keine Aeroeffekte unterstützt von Reinhardhttp://www.svenkubiak.de/2010/01/24/von-spiegeltreibern-werden-keine-aeroeffekte-unterstutzt/#comment-4153 Reinhard Sun, 22 Jan 2012 15:59:18 +0000 http://www.svenkubiak.de/?p=3127#comment-4153 Danke für die Tips, aber mein Problem kann so nicht gelöst werden: 1. brauche ich LogMeIn denn ich betreue 5 Maschinen aus der Ferne, also kann ich nicht drauf verzichten, LogMeIn hat sich seit Jahren bewährt und 2. von diesen 5 weisen nur zwei das Problem auf, auf den anderen drei gibt es kein Problem. Die Treiber sind die selbe, allerdings haben die jeweils andere Grafikkarten. Danke für die Tips, aber mein Problem kann so nicht gelöst werden: 1. brauche ich LogMeIn denn ich betreue 5 Maschinen aus der Ferne, also kann ich nicht drauf verzichten, LogMeIn hat sich seit Jahren bewährt und 2. von diesen 5 weisen nur zwei das Problem auf, auf den anderen drei gibt es kein Problem. Die Treiber sind die selbe, allerdings haben die jeweils andere Grafikkarten.

]]> Kommentar zu NoSpamNX von kubihttp://www.svenkubiak.de/nospamnx-en/#comment-4148 kubi Sun, 15 Jan 2012 09:38:07 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4148 @steve Thanks a lot for debugging! Fix is on its way. @steve
Thanks a lot for debugging! Fix is on its way.

]]> Kommentar zu NoSpamNX von Steve Munrohttp://www.svenkubiak.de/nospamnx-en/#comment-4147 Steve Munro Sun, 15 Jan 2012 05:27:14 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4147 Yes, that was the problem. Once I changed the activate routine to set a value for commentid if the key already existed, everything worked fine. The bug basically is that the activate logic only sets values if the array or a key within it is missing, not if it already exists. Obviously you don't want to reset things like the blacklist and the count, but I am not sure what the purpose of a never changing commentid or salt field would be. Yes, that was the problem. Once I changed the activate routine to set a value for commentid if the key already existed, everything worked fine.

The bug basically is that the activate logic only sets values if the array or a key within it is missing, not if it already exists. Obviously you don’t want to reset things like the blacklist and the count, but I am not sure what the purpose of a never changing commentid or salt field would be.

]]> Kommentar zu NoSpamNX von Steve Munrohttp://www.svenkubiak.de/nospamnx-en/#comment-4146 Steve Munro Sun, 15 Jan 2012 05:19:26 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4146 I have now verified that the value of commentid is null, but that salt has a value. Looking at your initialization code, you only drop the array nospamnx if the plugin is uninstalled, not if it is deactivated. This preserves the blacklist and count info. However, the code to actually assign a value to commentid is only executed under two conditions -- either the whole array does not exist and it must be created, or the array exists but the key commenid does not. If commentid is already defined, then the code to set a value is not executed. This also means that the commentid value is permanent. You used to have an option to refresh the secret key, but this is no longer present. I am going to force this function to execute as part of the activate routine to see if this fixes the problem. I have now verified that the value of commentid is null, but that salt has a value. Looking at your initialization code, you only drop the array nospamnx if the plugin is uninstalled, not if it is deactivated. This preserves the blacklist and count info. However, the code to actually assign a value to commentid is only executed under two conditions — either the whole array does not exist and it must be created, or the array exists but the key commenid does not. If commentid is already defined, then the code to set a value is not executed. This also means that the commentid value is permanent. You used to have an option to refresh the secret key, but this is no longer present. I am going to force this function to execute as part of the activate routine to see if this fixes the problem.

]]> Kommentar zu NoSpamNX von Steve Munrohttp://www.svenkubiak.de/nospamnx-en/#comment-4145 Steve Munro Sun, 15 Jan 2012 04:01:50 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4145 The plugins active on my site are NoSpamNX 5.0.0 Jetpack 1.2.2 WP Mobile Pack 1.2.4 WP Touch 1.9.37 Comment Move 1.0 WP-chgFontSize 1.8 I am running Twenty-Ten 1.2 None of these plugins should go near the comment field as it is generated (Comment Move is for assigning comments in the database to a new thread). Yes, I see the special hidden fields you are generating after the timestamp field, but as you say, nothing is replacing the comment itself. I put some trace code into the plugin, and can verify that the replaceCommentField function is being called, but that the test immediately following fails causing the original field to be returned rather than the updated one. This means that the commentid field must be null. I will keep digging and see if I can figure out why. The plugins active on my site are
NoSpamNX 5.0.0
Jetpack 1.2.2
WP Mobile Pack 1.2.4
WP Touch 1.9.37
Comment Move 1.0
WP-chgFontSize 1.8
I am running Twenty-Ten 1.2

None of these plugins should go near the comment field as it is generated (Comment Move is for assigning comments in the database to a new thread).

Yes, I see the special hidden fields you are generating after the timestamp field, but as you say, nothing is replacing the comment itself.

I put some trace code into the plugin, and can verify that the replaceCommentField function is being called, but that the test immediately following fails causing the original field to be returned rather than the updated one. This means that the commentid field must be null.

I will keep digging and see if I can figure out why.

]]> Kommentar zu NoSpamNX von kubihttp://www.svenkubiak.de/nospamnx-en/#comment-4142 kubi Sat, 14 Jan 2012 21:12:44 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4142 @steve I did take a look at your blog and the invisble fields are added correctly, except for the comment replacement. Take a look at my other blog http://play.svenkubiak.de which also runs on TwentyTen. There it is replaced correctly. Do you have any other Plugin that might interfer with the replacement? @steve
I did take a look at your blog and the invisble fields are added correctly, except for the comment replacement. Take a look at my other blog http://play.svenkubiak.de which also runs on TwentyTen. There it is replaced correctly. Do you have any other Plugin that might interfer with the replacement?

]]> Kommentar zu NoSpamNX von Steve Munrohttp://www.svenkubiak.de/nospamnx-en/#comment-4141 Steve Munro Sat, 14 Jan 2012 20:32:26 +0000 http://www.svenkubiak.de/?page_id=2110#comment-4141 Since I have enabled version 5, I have noticed a jump in comment spam that is getting through. I know that the plugin is active because I can trigger it by entering blacklisted text, but it is harder to test if the hidden fields are trapping the bots or not. In fact, when I look at the source of the displayed page, there is only one hidden field, and you seem to depend entirely on the timestamp test (new in this version) to detect spam, not the bogus comment fields you used before. They are not being generated now. I am running WP's Twenty-Ten theme (which I remember caused problems before) on WP 3.2.1. Since I have enabled version 5, I have noticed a jump in comment spam that is getting through. I know that the plugin is active because I can trigger it by entering blacklisted text, but it is harder to test if the hidden fields are trapping the bots or not. In fact, when I look at the source of the displayed page, there is only one hidden field, and you seem to depend entirely on the timestamp test (new in this version) to detect spam, not the bogus comment fields you used before. They are not being generated now.

I am running WP’s Twenty-Ten theme (which I remember caused problems before) on WP 3.2.1.

]]> Kommentar zu NoSpamNX 4.0 von NoSpamNX 5.0 | svenkubiakhttp://www.svenkubiak.de/2011/03/05/nospamnx-4-0/#comment-4139 NoSpamNX 5.0 | svenkubiak Sat, 14 Jan 2012 09:51:52 +0000 http://www.svenkubiak.de/?p=3517#comment-4139 [...] aktualisiert und auf die Version 5.0 angehoben (Version 4.0 gab es übrigens vor fast einem Jahr). Die neue Version ist ein recht großes Update, welches als wohl wichtigste Änderung die [...] [...] aktualisiert und auf die Version 5.0 angehoben (Version 4.0 gab es übrigens vor fast einem Jahr). Die neue Version ist ein recht großes Update, welches als wohl wichtigste Änderung die [...]

]]> Kommentar zu 16104 Spambots in einem Jahr von Markushttp://www.svenkubiak.de/2012/01/10/16104-spambots-in-einem-jahr/#comment-4135 Markus Wed, 11 Jan 2012 01:53:26 +0000 http://www.svenkubiak.de/?p=3684#comment-4135 Bei der Gelegenheit sage ich mal DANKE! für dieses Plugin, es leistet seit seinem Erscheinen in allen meinen Blogs hervorragende Arbeit. Bei der Gelegenheit sage ich mal DANKE! für dieses Plugin, es leistet seit seinem Erscheinen in allen meinen Blogs hervorragende Arbeit.

]]> Kommentar zu NoSpamNX von Jahresabschluss 2011 » exscribo.dehttp://www.svenkubiak.de/nospamnx/#comment-4124 Jahresabschluss 2011 » exscribo.de Sat, 31 Dec 2011 12:25:12 +0000 http://www.svenkubiak.de/?page_id=1875#comment-4124 [...] 115 Seiten, 96 Kategorien, 1859 Schlagwörter, 4396 Kommentare.Und zum guten Schluss hat das Plugin NoSpamNX insgesamt 8895 Spambots abgehalten, was einen Schnitt von 16 ergibt. Ich möchte echt allen [...] [...] 115 Seiten, 96 Kategorien, 1859 Schlagwörter, 4396 Kommentare.Und zum guten Schluss hat das Plugin NoSpamNX insgesamt 8895 Spambots abgehalten, was einen Schnitt von 16 ergibt. Ich möchte echt allen [...]

]]>