I'm currently experimenting if and how presenting users links to other content of this site affects the site navigation (and how you may have guessed: Yes, I got myself a Google Analytics account, too). First I decided to display related articles beneath each articles. Now I'm trying a "Most popular" block that displays the top five pages visited within the last three days. Here's how I did it.
I added support for Gravatars today. If you own a gravatar, it will be displayed aside your comment. The following images have a special meaning:
 |
This is displayed, if you do not have a gravatar. It show's a plant called "Sonnentau" in German, scientifically it is called Drosera something. It grows in the bog and eats insects. Nothing about your character or your favourite meal is implied by that. |
 |
And this is me ;-). |
Writing about the base tag and stupid search engines I completly forgot that RSS doesn't accept relative links - for a good reason of course. This caused at least Bloglines to get a little bit wild about my feed and I'm sorry for the inconveniences this may have caused.
Anyhow, I decided to get rid of the problem once and for all by turning relative links into absolute when writing the feed. This is how I did it:
If you read this, most presumable through a RSS feed, this page has successfully moved from WordPress 1.2 to Drupal 4.6.3. Regard this as beeing a simple test. I'll cover the why's and how's later on.
A while ago I hacked my WordPress installation to ask the user a stupid question before committing a comment. However, there's already a plugin, that does exactly this.
I validated my feed today and got a strange error: "Relative paths not allowed in <content:encoded>". I checked the according entry over and over but all links were correctly set absolute with "http://".
Were they? No! Finally I figured out that one link was written as <a href=" http://...">. Notice the little blank before "http://"? That caused the error.
There's a wave of contact form spamming going around and it hit the Comic Marktplatz, too. The main purpose of this attack is to figure out websites providing forms that can be misused to send spam, effectivly turning them into open relays. This affects not only contact forms, but also blog comments.
Does anyone know a CMS that is able to distinguish between an author of an article and the publisher? These two roles are commonly treated as the same, which is suitable for a blog or company site. However, for a newspaper this isn't the case.
During the last days, I was heavily suffering from comment spam. And Spam Karma for some reason wasn't able to handle it.
Actually, I decided to no longer trust in anti-spam plugins but rely on security through obscurity. This is: I wrote my own simple but hopefully effective captcha. I decided to rely on simple questions rather than distorted images, since they bring up accessibility problems - it is impossible to read that image if you are blind.
