http://wordpress.org/extend/plugins/lastfm-records/

What has been done?

* complete rewrite, can be used under PHP4 again!
* most of the work is done in javascript, as the php code waited for a response from last.fm which slowed down your weblog
* support for wordpress 2.8/2.8.1, including the automatic updating
* you can set an auto refresh time (in minutes), if you do, the code will go back to last.fm and update the cd covers dynamically in the webpage
* you can specifiy your time offset from GMT
* new stylesheet built, as a starting point for your own splendid work

* the javascript in the zip at the Wordpress Plugin Directory can be used without Wordpress, see

http://jeroensmeets.net/projects/last.fm/

for info and a how to.

There’s still some work to do, and some things have changed:

* the option to use

<?php lastfmrecords_display(); ?>

has been dropped. Please use the javascript call instead.

* the option to use

[ lastfmrecords|overall|4]

in Wordpress pages & posts isn’t working correctly at the moment. Haven’t decided yet what to do about this, have no support requests about this. Anyone using it?

* the offset setting seems broken. Will look into that for version 1.5.4
* using other periods (last week, etc.) will be back in has been added to version 1.5.3

Related posts:

1. Version 1.4 of Last.Fm Records released

jQuery schoot te hulp: dit scriptje vult ieder HTML formulier of enquete in. Sleep deze link naar je bladwijzerbalk en klik erop als je een formulier wilt testen. Als altijd is de versie 1.0beta.

Vul formulier met dummy data

Bij een klik op de bladwijzer wordt het formulier met dummy data gevuld en scrollt de pagina helemaal naar beneden. Er wordt alleen (nog) niet op de “volgende pagina” knop geklikt.

No related posts.

Create script to parse incoming mail

<?php
  $data = file_get_contents("php://stdin");
?>

Add a new email address to Postfix configuration

sudo vi /etc/aliases

and add the following line (everything on one line)

email+to+redirect: "| php -q /home/user/full/path/to/your/new/script.php"

Apply the changes to the aliases by running

newaliases

To make sure Postfix will pick up the newly added alias soon. If you’re in a hurry, do a

/etc/init.d/postfix reload

Aaaaaah!

One thing that took some time to figure out: my php script ran ok from the prompt, I had supplied it with test data and I saw all the expected data in my database. Yet, when I triggered the script by sending an email to the new address, Postfix bounced it right back at me, saying

The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.

< xxx.yyy #5.0.0 X-Postfix; Command died with status 255: " php -q /home/user/full/path/to/your/new/script.php">

In the end, the reason for this error is simple. It is Postfix telling me PHP stopped executing the script as it found an error. In my case, the error occured when the script ran as user Nobody. When tested from the prompt, I didn't get the error, as the user had sufficient rights.

No related posts.

After finding the script that caused all my stress, and several ftp accounts on my account that I didn’t create, I find out on several forums that this is something specific to Servage and its lack of security.

I find it unbelievable that you haven’t notified your clients, or at least ran a script on all your servers to see who got infected.

<postscript>after cleaning up and re-chmodding the whole tree before Christmas, this thing repeated itself just after the holidays. Apologies to those who ran into the silly javascript. I have moved to a new hosting account and switched to VPS.</postscript>

No related posts.

As we’re approaching the new year, here is my resolution: one codebase for all, starting today with a basic object that can be used as-is, or with some additional programming, for platforms as Wordpress and Drupal. This also means that my Wordpress plugins will be built on this code once it gets out of beta (hey, even Chrome did!).

In case you’re wondering: yes, the covers on the top right of this page are there thanks to this new code. And no, it’s not a Wordpress plugin or widget yet, I wrote it directly in themes/sidebar.php

I’m releasing this code under GPL, so it is available to use in your own projects. If you do, I ask you to

1. keep my info in the javascript file
2. change the last.fm API key
3. let me know where you are going with it

Once installed, the javascript hands you one object you can configure and run, like this:

jQuery(document).ready( function() {

  // last.fm username
  lastFmRecords.setUser('hondjevandirkie');
  // id of the div element where script can add covers
  lastFmRecords.setPlaceholder('lastfmrecords');
  // image to show while loading images or when image not found
  lastFmRecords.setDefaultThumb('./lastfm_logo.jpg');
  // TODO: value is ignored at the moment
  lastFmRecords.setPeriod('smart');
  // TODO: value is ignored at the moment
  lastFmRecords.setStyle('lightbox');
  // number of covers, at the moment max. 50
  lastFmRecords.setCount(20);
  // refresh interval (get fresh data from last.fm)
  lastFmRecords.setRefreshMinutes(1);
  // GMT offset
  lastFmRecords.setTimeOffset(1);
  // log to console
  lastFmRecords.debug();

  // run
  lastFmRecords.init();
});

Most options come from my earlier projects; the refresh is new. And best of all, I found out how to get JSON from last.fm. This means jQuery can make the requests, so all requests now go directly from the browser to last.fm, without a data provider in PHP on your own server.

So what do you need to get this running?

• include jQuery
• include last.fm.records.js
  (see download link below)
• a last.fm username (you’re free to use mine when you like Randy Newman)
• a div on the page where the script can put the HTML in
  (default: <div id=”lastfmrecords” />)

You can download the beta of Last.Fm Records 3.1 here.
UPDATE: see this page for the javascript file. It’s in the Wordpress package, but can be used alone.

No related posts.

Surely this won’t have the same use it has on mobile devices. But it finally makes the NSFW warnings superfluous.

Anyway, I enjoyed myself writing a demo showing wiki articles on places in your neighborhood.

No related posts.

The solution I built is solved in one browser for now, Firefox. The javascript copies the image to a canvas element and paints the solution on the canvas. Proudly I present: mazeQuery.

UPDATE (2009/05/23): it works in Chrome 2.0 on Windows.Op het “Signals vs. Noise” weblog van 37signals stond een uitdaging — de eerste die een (plaatje van een) doolhof oplost krijgt een korting van $50 dollar. De eerste (grappige) reactie was vrij vertaald “Daar is geloof ik een jQuery plugin voor.” en dat maakte iets in me los: dit wilde ik in een browser oplossen.

Mijn doolhofoplosser werkt op dit moment in 1 browser: Firefox. De javascript kopieert het plaatje naar een canvas element en tekent de oplossing op de canvas. Trots presenteer ik: mazeQuery.

UPDATE (23 mei 2009): het werkt nu ook in Chrome 2.0 op Windows.

No related posts.

This evening I was frustrated with an array in jQuery and as I was working in Chrome, I couldn’t use Firebug. So I tried to debug the old fashioned way: by displaying an alert in the each() loop. On the second alert box, Chrome added a checkbox: ‘Prevent this page from creating additional dialogs’. Really helpful.

Related posts:

1. Programming Brain Teaser

It’s nice to have a couple of tabs open without the airconditioning going into overdrive. Let’s explore.

No related posts.

• make it work in IE
• option to show album title and artist next to image
• option to use it with lightbox plugin (not included)

I’ll be answering some of the questions in the comments later, but now it’s Sunday evening and I’m off to bed to have a good night of sleep before my first day at work tomorrow.

Related posts:

1. Run for cover 2.0