I moved everything from 1und1.de to strato.de because the old web host was too expensive and had crappy service, now the new web host is less expensive and still has crappy service and on top of all that mod_rewrite is not working and producing internal server errors. Turns out there are a lot of unhappy strato.de users facing the same problem.
All my links you find via search engines have permalink structure and are now broken since strato.de just doesn’t offer mod_rewrite with any of their web hosting packages, at least that is what I am led to believe. This is easily the death of any blog if suddenly none of the 1000s of links search engines have cataloged stop working altogether.
How such a simple feature can not be part of a “PowerWeb Advanced” package, esp. when Strato.de advertizes their webspace to be Wordpress friendly is beyond me. If you have made similar experience, feel free to comment.
For now I am using this plugin which (ab)uses the 404 error document as a workaround to use permalinks without mod_rewrite.
I was just wondering how useful it would be to combine GaMerZ’s plugin WP-Ban with AKismet’s IP data, i.e. store all IPs from AKismet in a table before flushing the spam and keep count how often an IP is used for spamming, e.g. take a look at this:
72.232.2.188
72.232.207.26
72.232.218.186
72.232.250.10
72.232.93.212
You will notice that 72.232.*.* is quite a spammer and with enough statistical data we could let WP-Ban know that and avoid having to deal with those spam comments at all. If you want to get rid of a problem, get rid of the source. AKismet is all nice and dandy but it doesn’t do enough. Storing the IPs in a table and keeping count will eventually lead to a network of IP ranges used for spamming and why not ban those ranges? What would be the downside? False positives? Well, I couldn’t care less if a few false positives will mean less to no spam, you have to make sacrifices for the greater good.
The good folks over at wordpress.com invited me to their latest WordPress goodness and I must say it rocks! I am not certain for what exactly I am going to use ihad.wordpress.com since I still have Wordpress! Bad pun, forgive me.
At a first glance the thing that I am missing most is the ability to add plugins (e.g. wp stats, amazon, flickr, live archives etc.) and the theme editor which means you are stuck with the themes available for now. I am sure there will be lots more in the future and more functionality will be added, too – although maybe that will come with a fee… time will tell.
rboren hat auf der codex.wordpress.org Seite ein aktualisiertes .pot Update hochgeladen und die Änderungen sind wie gewohnt hier erhältlich.
Endlich ist u.a. auch das (more…) lokalisiert! Der Link Manager wird aus der Datenbank generiert, daher wird es noch etwas dauern, bis auch dieser komplett lokalisiert werden kann. Die Schwierigkeiten mit Umlauten in von WP verschickten emails sind auch schon in Arbeit.
Patience is a virtue! ;)
.po / .mo
Stand: 05.09.2004 (CVS)
ps: hier läuft die nightly 05-09. das .mo greift aber nur wenn die CVS verwendet wird. In einer der nächsten nightlies werden die Neuerungen dann natürlich auch aktiv sein. Ansonsten kann das aktuelle mo problemlos vewendet werden.
Wenn ihr Bugs melden wollt, oder auch fehlende Übersetzungen, die trotz vorhandener deutscher Einträge nicht angezeigt werden (wie z.B. “x Comments” auf der Kommentar Seite) , dann benutzt bitte die offizielle Bugtracker Seite:
Unter http://mosquito.wordpress.org/ geht’s direkt zur Mosquito Klatsche.
