Archiv für die Kategorie „WordPress“

Akismet Spam

Donnerstag, 9. November 2006

Ich habe vorgestern aus Verzweifelung das Akismet Spam Plugin von WordPress ausprobiert und bin hellauf begeistert. Jeder gepostete Kommentar wird mittels des Akismet Webservice auf Spam Eigenschaften geprueft. Negativ bewertete Postings werden nach 14 Tagen geloescht, koennen aber so lange im Akismet Menupunkt (Verwaltung->Akismet Spam) gesichtet und gegenbenfalls als „gutartige“ umgestuft werden.
Das Plugin ist ab WordPress 2.0 bereits installiert und muss nur noch ueber das Adminstrationsmenu in WordPress (Plugins->Plugins) aktiviert werden.

Zusaetzlich benoetigt man einen API Key, denn man als registrieter Nutzer umsonst fuer nicht kommerzielle Zwecke erhalten kann.

Mit diesem Key kann man den Akismet Spam Dienst ueberigens auch fuer andere Applikationen als  WordPress verwenden. Es gibt unter anderem Implementierungen in Ruby, Python, Perl, Java, und PHP.
Fazit: Als Betreiber einer Site, die selten bis nie legitime Kommentare erhaelt, kann ich ich Akismet wirklich waermsten empfehlen. Installation is vollkommen schmerzfrei,in 5 Minuten erledigt und das staendige wegmoderieren von Reklame fuer englische Mobilfunkanbieter entfaellt vollstaendig. Wie sich sich das Plugin bei einem hohen Volumen legitimer Kommentare verhaelt, kann ich leider nicht beurteilen.

Displaying Source Code in WordPress

Dienstag, 7. November 2006

I needed to post some source code on WordPress. I had no idea how painful this would be. There’s a number of plugins that are supposed to handle this, but that canonical source code plugin doesn’t seem to exist. The one that seemed to fit my needs best was Code Viewer because of the following features:

  • lets you maintain source code in a external files, only maintaining references to the files in the editor
  • automatically includes download link to the external files
  • line numbering

A guy called AJ added scrollable text areas and the capability to select which lines to display like this: 1,3-7,15 in updated versions. Both versions have at least two disadvantages I’ve stumbled across:

  • they can’t be used with the WYSISWIG Editor, because the built-in tinyMCE editor really goes out of it’s way to make sure it screws up anything remotely resembling source code.
  • they require their own CSS styles that can either be included from the header template or appended to the end of the default.css stylesheet. Both options require editing „default“ files, which I think is bad style.

A third guy called Håkan Carlström tries to address these issues, but unfortunately, I wasn’t able to get his version of the plugin code to work at all.

I looked at the different versions and but together my own melange. Caveat: I have no idea what license any of the three release the code under, but I’ll get back to you on that…

The reason why the first two versions don’t work in the WYSIWYG editor, is because they rely on xml tags like this:


and the WYSIWYG editor just can’t cope with unfamiliar tags. The editor will also consistantly screw up the string:


but that’s another story. Håkan version of the plugin tries to avoid the angled brackets by using square brackets like this:

a tad too verbose for my taste. A nice feature of his plugin is the capability to dynamically link in the necessary style sheet. Too bad I can’t get it to work…

So here’s my version. It can be used from within the WYSIWYG editor because it uses source as the attribute name instead of src and square brackets like this:


So anyway, this is what you end up getting:

[viewcode source=“arg.src“ scroll=“yes“]

Yes, it’s true, I spent the larger part of the afternoon sifting through *argh* php code. And now this. So: DO NOT USE THIS PLUGIN WITH PHP CODE!

What else didn’t I get working? Glad you asked: including a link to the Coder Viewer stylesheet doesn’t work, because of an unseen entity from deep within WordPress that filters out link tags.

That being said, you can download the semi-functional plugin here.

So here’s the css with some modifications I’ve made, you’ll need to botch these styles into some other stylesheet you’re already including or include it seperately in the header:

[viewcode source=“code-viewer.css“ link=“yes“ scroll=“yes“]

Included on this page using the actual Code-View plugin!!

So if there’s anything I learned from this experience is that while I already disliked php for having $variables and unecessary semicolons, I had no idea how bad it really sucks: