drdave
Forum Replies Created
-
Forum: Alpha/Beta/RC
In reply to: Since upgrade, comments not showingNote: only upgrading to SK2.1+ is necessary. The compatibility plugin was there as a temporary fix for older version and is therefore no longer necessary.
Forum: Fixing WordPress
In reply to: No more comment countingJust to put the final word on this:
– WP 2.0 is *not* compatible with SK 2.0. In order for the two of them to play nice, you need to install SK 2.1 (now final), available on the main site at: http://unknowngenius.com/blog/wordpress/spam-karma/
– You do not need the compatibility plugin with SK 2.1 (it was only used to make SK 2.0 compatible).
– If you had previously miscalculated comment counts on certain posts, follow the instructions above to have SK2.1 re-parse these comments and update the comment count.
Contact me if you bump into any problem…
Forum: Plugins
In reply to: How to add redirect to SK2 after comment?Actually, this is not quite accurate: SK2 does redirect commenters to the original page after they comment. The line of code you mention is only for fringe cases where the commenter has had to fill in a captcha (or other “safety” measures) to complete his posting. This should be a rare occurrence.
This will be worked on, but is less than trivial to fix (URLs need to be stored in the DB, as a commenter may decide to go fill in the captcha or otherwise unlock the comment, long after it was posted)…
Forum: Plugins
In reply to: Spam Karma 2 TroubleBhooshan:
Have you tried the “Reset All Tables” button under “advanced options”. It should re-create these tables that were apparently never created for some reason… If it doesn’t, it will at least spit out an error message. Please copy this message and send it to me.
Forum: Installing WordPress
In reply to: Flickr Aidez moi !Je pense qu’il serait préférable de lire en détail la documentation de Flickr avant tout.
Autrement, regarder du coté des plugins pour WP: il y en a surement un qui fait ça automatiquement.Forum: Plugins
In reply to: Spam Karma – blocking EVERYTHING???Wow, seems like there was much talking round me… and none of my faithful legion of evil minions bothered to inform me…
Well, I really don’t have time to get into a debate about everything that’s been said, plus, for some complicated reason way too long to explain, I am boycotting the forums, but I’ll try to clear up a few misunderstanding and add my two yens:
1) As of this week (the release of WP 1.5.1 to be precise), SK 1.x is absolutely no longer supported. While I consider it a reasonably fine piece of code, it also contained many small bugs and shortcomings, all of which have been addressed in a way I saw fit, and made into SK 2. If, for one reason or another, you do not want to upgrade, feel free to use SK 1 (or another spam plugin for all I care), but please, DO NOT COME WHINING THAT IT ISN’T WORKING. SK 1.x is obsolete. Period.
2) Now, SK2 is not quite perfect yet, and it’s in the very final stage of beta-testing (frankly more stable than quite a few “release”-grade software out there), but every single issue pinpointed with SK1 was addressed. So far, it has yielded an extremely low rate of false positives, all of which were either due to a bug that was fixed, or some particularly blurry case, where even a human could have been fooled.
3) The point about “boastful” messages and the fact bots don’t read them is totally true. Yet, most boasts in real life hardly serve a purpose of impressing whoever you are boasting to. They are merely there as a way to channel anger or irritation at something. Spammers are an excruciatingly annoying breed, boasting of how many spams were squashed doesn’t achieve much purpose, but it sure feels nice. As for any sort of accusatory tone in the “comment denied” message, it was *long* removed from SK. Any blog still showing that message is badly out of date. There again, I can’t be held responsible for people who do not realize a plugin needs to be updated every once in a while, especially when it’s dealing with stuff like spam.
3) I personally think that the “manually edit htaccess” method is a ridiculous waste of time (for every daily minutes you spend doing that, may I remind you it takes the spammer a tenth of a second configuring his bots). I also have some serious reserve with the technical aspect (performance hit etc) of this method.
Referrer Karma is indeed a good way to automate that, and works nicely with SK (it will be soon improved to work with SK2), but it most definitely isn’t perfect and yields many unavoidable false positives too (except these are not a big problem, since they merely mean redirecting the visitor, which is hardly noticeable).
4) Regarding false positives: keep in mind that practically every single comment mistakenly stopped by SK would likely have been mis-identified by most other spam plugins as well. Not trying to launch a war of the plugins here, just pointing out that there are *no* perfect plugin out there, and what usually screws up SK (or used to), would do the very same to any of the many plugins using similar detection devices. For more details, please read my lengthy entry on the topic:
http://www.unknowngenius.com/blog/wordpress/spam-karma/false-positives/5) I have said it before (in a message that was mysteriously edited out of the forums), but frankly: I don’t care if you use SK or not.
I mean, if you encounter a bug, report it to me, and help me work through it, I’ll fix it. I think quite a few people should be able to testify for that.
I strive to improve it, and for no other reason than: a) personal pride b) it is useful to me and people I care about (including the community at large).
As you can see, “business plan”, “financial incentive” or anything that would pertain to keeping “customers” happy doesn’t appear in my motivations. So some of the whiners would better start realizing that this is free software, and while I’m sure grateful for the support, donations and thank-you notes from satisfied users, I am not about to lose sleep over the fact that some users just do not like it.
If you feel like there’s a better solution out there, just go for it! As long as you are making an informed choice and weigh the pros and cons of whatever method you use, I am 100% in favour of plugin diversity: it is the #1 way to fight spam!6) As for the person who, I gather, has been making some generalization about how SK was universally reviled: I guess we don’t quite live in the same world… A quick search around google will show you that there are many thousands of people currently running it: that’s a lot of masochistic people, huh… additionally, very conservative estimates would give a total number of spams stopped so far by SK, way into the millions: with even a few hundred false positives (which is way less than ever was reported or mentioned to me), that is a success rate somewhere in the 99.9%… I don’t really see any reason to hide my head in shame for that.
I note, however, that except for the occasional moron posting insults on my blog because of what he assumes to be personal censorship geared directly at him (and usually doing so at the bottom of the very page explaining why it’s not), and the people contacting me in good-faith for help solving their bugs, most of the dissatisfied users seem to consider it incredibly more productive to whine about it in private or on their own blog, rather than ever contacting me… I still fail to see if this kind of people consider it is my duty to browse the web day and night, looking for such post and bending over backward to help them, or if they just need to vent their anger and frustration at some random person/software.
But anyway: don’t worry for me, my skin is much thicker than that. I’ve long stopped caring too much, and who knows I might end up stopping to care at all (no, not quite yet).
As I said and will say once again: if you have an issue with SK2 (and SK2 alone) and want it solved, simply contact me (preferably by email, or by leaving a comment on the SK page) and I’ll do my best to address it. On the other hand, if you just want to whine about it: feel free to go ahead, see if I care.
Forum: Fixing WordPress
In reply to: Weird Spam Karma IssueHi there,
For anybody experiencing any sort of issue with SK1 (whether with false positives, or that pesky captcha display), I’d recommend upgrading to SK2 pre-alpha (very soon to become alpha). Seeing how these issues (and much more) have been addressed and there hasn’t been any major bugs reported so far, there’s little to lose here.
Beware that you need to upgrade your WP install to fix a bug present in the original 1.5 release (see details here: http://unknowngenius.com/blog/wordpress/spam-karma/dev/)…
For those 100% happy with their current install of SK, I suppose you can wait for the first public beta (itself waiting on WP 1.5.1 release, which should be rather soon). But feel free to take the jump now: there is quite a lot of improvement to be enjoyed with this new version.
thanks everybody…
Forum: Fixing WordPress
In reply to: spam karma doesnt work..I would be immensely curious to know why my reply to John1000 was unilaterally erased from this thread without notice.
Granted it contained [duly tagged] profanity, but that doesn’t change a thing to the spirit of the rest, which I felt was quite important as to the matter at hand…
It would have been nice to at least contact me by mail about it.Forum: Plugins
In reply to: Spam Karma 1.5 (WP 1.2 compatible)…Thanks moose…
Well, no real reason it wouldn’t really play nice with others. But there’s really no point using it with any other Plug-ins. Actually, using certain plugins could weaken it, in that even if SK silently moderates or deletes a spam, it is still possible for another plugin to unmoderate it or pester the admin with notification email…
One of the goal of SK is to be as exhaustive as possible. As such, I know no efficient trick at the moment that is not already incorporated (there might be, but I haven’t seen them)…
Overall, I’d recommend turning off any other spam plugin you have, unless you know it works in a notably different way. I would even go further and recommend turning off the “Use WP Discussions” checkbox in SK Options (it tells the plugin to completely ignore WP’s diagnostic based on the ‘spam words’ list and number of links) as WP’s built-in checks are either redundant with SK (number of links) or likely to create many false positives (spam words).Forum: Fixing WordPress
In reply to: german weekdayAccording to the doc:
http://www.php.net/date
“D” (mind the cap) will display the day of the week in your local setting (German, provided your host is set up for German localization, otherwise, that can be set locally).
HtHForum: Fixing WordPress
In reply to: Display the name of the Month on the monthly archibstovold,
Glad you found a solution (definitely more elegant than my php hack)…
however, you said:Of course, I wouldn’t need to do this if I wasn’t using mod_rewrite, as the $m, $y and $p variables would be available.
As I said, this is not completely true: you can easily access month, year and day through $_REQUEST[‘monthnum’], $_REQUEST[‘year’] and $_REQUEST[‘day’]
Actually, that’s all the mod_rewrite does: turns your slash-separated strings into POST arguments…Forum: Fixing WordPress
In reply to: Display the name of the Month on the monthly archiOoops, just realized one of the template string above is wrong, it should be:
$day_tmp = "D F j, Y";Forum: Fixing WordPress
In reply to: Display the name of the Month on the monthly archiI bet there’s an easier way, using WP API and internal variables, but I do not know enough about WP yet…
But actually, the PHP programming to display these info is not so heavy, depending on what you want…
whether you use mod_rewrite or not, all archive parameters are passed to the page in the$_REQUEST[]variable.
The following bits of code should display respectively the day, month and year (if any) of the category being displayed:
<?php echo $_REQUEST['day']; ?>
<?php echo date("F", strtotime($_REQUEST['monthnum'])); ?>
<?php echo $_REQUEST['year']; ?>
However, the previous bits are of little use if you have a common template for month and year archives (since you won’t know when to display either date format).
This slightly more complex block would solve the problem:
<?php
$day_tmp = "D F G, Y";
$month_tmp = "F Y";
$year_tmp = "Y";
if (! empty($_REQUEST['day']))
echo date($day_tmp, strtotime( $_REQUEST['year'] . "-" . $_REQUEST['monthnum'] . "-" . $_REQUEST['day']) );
elseif (! empty($_REQUEST['monthnum']))
echo date($month_tmp, strtotime( $_REQUEST['year'] . "-" . $_REQUEST['monthnum'] . "-01") );
elseif (! empty($_REQUEST['year']))
echo date($year_tmp, strtotime( $_REQUEST['year'] . "-01-01") );
?>
With this one bit, you do not have to worry about any check… it will only display date info when they are available.
All you have to do is change the template format for each archive type (the$day_tmpetc. at the beginning). They use PHP’sdate()syntax, which is pretty easy and completely documented here: http://www.php.net/date
Hope this help.